[Touch-packages] [Bug 1438662] Re: Calendar sync is not happening
I installed the last calendar patch too, and after a reboot, while trying to sync my calendar with Google, I got the error fail to sync. The version of the package syncevolution is 1.5~rtm-0ubuntu4. It runs on a bq phone (manufacturer version updated with last patches). The log is : From file /home/phablet/.cache/upstart/sync-monitor.log: syn requested for account: yyy@gmail.com calendar Pushed into queue with immediately sync? true Sync is running false Request sync Sync requested service: yyy@gmail.com calendar Configure account for service: yyy@gmail.com calendar disabled start configure for services (calendar) config session created google-calendar-2 idle account config done yyy@gmail.com calendar [16/04/15 07:00] Start sync: yyy@gmail.com (calendar) Progress 0 Sync Report dir : /home/phablet/.cache/syncevolution/google_+calendar_+2-2015-04-16-07-00 end : 1429160451 error : error code from SyncEvolution fatal error (local, status 10500): no datastores active, check configuration peer : google-calendar-2 start : 1429160451 status : 10500 [16/04/15 07:00] Sync done: yyy@gmail.com (calendar) Status: 10500 Error: Unknown status Duration: 1s Sync requested service: yyy@gmail.com calendar Configure account for service: yyy@gmail.com calendar slow start configure for services (calendar) config session created google-calendar-2 idle account config done yyy@gmail.com calendar [16/04/15 07:00] Start sync: yyy@gmail.com (calendar) Progress 0 Progress 0 Progress 38 Sync Report dir : /home/phablet/.cache/syncevolution/google_+calendar_+2-2015-04-16-07-00-a end : 1429160453 error : error code from SyncEvolution remote, status 400: REPORT 'meta data': bad HTTP status: status 1.1, code 400, class 4, Bad Request peer : google-calendar-2 source-calendar__uoa__2-backup-after : -1 source-calendar__uoa__2-backup-before : -1 source-calendar__uoa__2-first : false source-calendar__uoa__2-mode : disabled source-calendar__uoa__2-resume : false source-calendar__uoa__2-status : 10400 start : 1429160452 status : 10400 [16/04/15 07:00] Sync done: yyy@gmail.com (calendar) Status: 10400 Error: Unknown status Duration: 1s All syncs finished New connection type: WLAN New connection type: WLAN New connection type: WLAN New connection type: WLAN New connection type: WLAN New connection type: WLAN New connection type: WLAN -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1438662 Title: Calendar sync is not happening Status in the base for Ubuntu mobile products: In Progress Status in Sync monitor for Ubuntu Touch: Invalid Status in syncevolution package in Ubuntu: In Progress Status in syncevolution package in Ubuntu RTM: In Progress Bug description: STEPS: 1. Install calendar 2. Step up your google account 3. Enable accounts to use calendar 4. Tap on the sync option in Calendar EXPECTED: I expect it to update my calendar and notifications ACTUAL: In .cache/upstart/sync-monitor.log I see lots of error : error code from SyncEvolution remote, status 400: updateAllSubItems REPORT 'list items': bad HTTP status: status 1.1, code 400, class 4, Bad Request and error : error code from SyncEvolution remote, status 400: REPORT 'meta data': bad HTTP status: status 1.1, code 400, class 4, Bad Request and sync doesn't happen We are assuming this is a change on googles side that affects us on both vivid and rtm. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1438662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443538] Re: mouse pointer invisible/disappears
This happened to me today.. got it back after waiting the screen to blank (screensaver) and waking it up. Does this work for you too? ** Package changed: xorg (Ubuntu) = xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed = Incomplete -- 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/1443538 Title: mouse pointer invisible/disappears Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Only way to get it back is reboot. If I switch to another VT and run xinit -- :1 I have a mouse on that X server but still no on the original one. Also since xinit only starts a single xterm and when I type in that xterm the mouse pointer gets invisible until I move the mouse my guess is that the mouse is always invisible is a problem with the X server and not with say unity. I have a mac book pro using only the intel driver. Is there any command I can use to force the pointer to be visible again ?? this has happened several times now and is starting to be a real problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 13 18:24:30 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-12-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:012e] InstallationDate: Installed on 2015-04-09 (4 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Apple Inc. MacBookPro11,2 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-13-generic.efi.signed root=UUID=f84ca03e-c0d4-45ad-80f3-c45d4ad106dd ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP112.88Z.0138.B14.1501071031 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-3CBD00234E554E41 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-3CBD00234E554E41 dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B14.1501071031:bd01/07/2015:svnAppleInc.:pnMacBookPro11,2:pvr1.0:rvnAppleInc.:rnMac-3CBD00234E554E41:rvrMacBookPro11,2:cvnAppleInc.:ct10:cvrMac-3CBD00234E554E41: dmi.product.name: MacBookPro11,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150330-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Apr 13 18:22:22 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40994 vendor APP xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1443538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441675] Re: screen brightness arrows no longer work after disconnecting external monitor
yeah, there was a dodgy commit in -12 that got reverted in -13 ** Changed in: xorg (Ubuntu) Status: Incomplete = Fix Released -- 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/1441675 Title: screen brightness arrows no longer work after disconnecting external monitor Status in xorg package in Ubuntu: Fix Released Bug description: Noticed after disconnecting external monitor today that the Fn-Left and Fn-Right keys, which normally 1) Trigger the display of a sun icon with a progress bar of the amount of supposed brightness the screen is supposed to have 2) actually changes the amount of brightness that the screen is supposed to have currently only does (1) (ie not (2)). Ubuntu 15.04 xorg: Installed: 1:7.7+7ubuntu4 Candidate: 1:7.7+7ubuntu4 xserver-xorg-video-nouveau: Installed: 1:1.0.11-1ubuntu2build1 Candidate: 1:1.0.11-1ubuntu2build1 Linux Hedy 3.19.0-12-generic #12-Ubuntu SMP Fri Apr 3 04:03:26 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 01:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] (rev a1) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Apr 8 10:50:17 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0689] Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0689] InstallationDate: Installed on 2014-07-09 (272 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 (20140708) MachineType: Acer TravelMate P273-MG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BA70_HC dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: TravelMate P273-MG dmi.product.version: V2.11 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.1+15.04.20150330-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Apr 4 03:31:26 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5278 vendor AUO xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1441675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798445] Re: can't discern between two files or folder with identical names
I just wanted to know what that status change means. Should users provide some proposal about how to implement it ? If this is the case, I should simply propose to display a tooltip showing the file path when mouse pointer hovers over it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/798445 Title: can't discern between two files or folder with identical names Status in Ayatana Design: New Status in Unity: Incomplete Status in Unity Files Lens: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Binary package hint: dash 1. create two folders/files with the same name (in two different locations). 2. press the BFB (Big Freakin Button aka Home Button) and search for that folder/file name see that there is no way to tell which folder/file is which. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: dash 0.5.5.1-7.2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Jun 16 17:50:38 2011 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dash UpgradeStatus: Upgraded to natty on 2011-04-21 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/798445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436074] Re: tab previews black [arale only]
** Branch linked: lp:~kubuntu-packagers/kubuntu-packaging/qtbase- opensource-src -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1436074 Title: tab previews black [arale only] Status in the base for Ubuntu mobile products: Confirmed Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: running vivid-proposed build 146 on arale When I swipe from bottom edge to reveal tabs, only the most recent tab has a preview. The other tabs are black where the preview should be. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440177] Re: page tearing
** Package changed: xorg (Ubuntu) = xserver-xorg-video-nouveau (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1440177 Title: page tearing Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: not even sure how i posted this, but the drivers could use some work when being run on an nvidia card, e.g. slow firefox performance with video (html5 flash) and general page tearing/lack of smooth motion. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3 Uname: Linux 3.19.0-11-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Apr 4 05:16:05 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0479] InstallationDate: Installed on 2015-04-03 (0 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Beta amd64 (20150402) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-generic root=UUID=47da01d8-0b6a-4af4-b5fb-ece8c1c75897 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd08/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-VM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Apr 4 02:27:23 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt Microsoft USB Optical Mouse MOUSE, id 8 inputMicrosoft Wired Keyboard 600 KEYBOARD, id 9 inputMicrosoft Wired Keyboard 600 KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1440177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443070] Re: mouse cursor is gone, when I move it to screen top border
** Package changed: xorg (Ubuntu) = nvidia-graphics-drivers (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1443070 Title: mouse cursor is gone,when I move it to screen top border Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: ubuntu 15.04 vivid beta2. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 12 20:25:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-12-generic, x86_64: installed nvidia-346, 346.59, 3.19.0-12-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-12-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c606] Subsystem: Samsung Electronics Co Ltd Device [144d:c606] InstallationDate: Installed on 2015-04-09 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: No journal files were found. MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4A/300E5A/300E7A/3430EA/3530EA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic root=UUID=dc79c911-9c4c-4665-be52-7156bc71272a ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 07QA dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 300E4A/300E5A/300E7A/3430EA/3530EA dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr07QA:bd04/20/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4A/300E5A/300E7A/3430EA/3530EA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300E4A/300E5A/300E7A/3430EA/3530EA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 300E4A/300E5A/300E7A/3430EA/3530EA dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.1+15.04.20150330-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 12 23:42:44 2015 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13897 vendor SEC xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1443070/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438662] Re: Calendar sync is not happening
@renatofilho : I tried again this morning after the OTA update on devel- proposed channel. So yes I've rebooted. My syncevolution version is : 1.5-0ubuntu4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1438662 Title: Calendar sync is not happening Status in the base for Ubuntu mobile products: In Progress Status in Sync monitor for Ubuntu Touch: Invalid Status in syncevolution package in Ubuntu: In Progress Status in syncevolution package in Ubuntu RTM: In Progress Bug description: STEPS: 1. Install calendar 2. Step up your google account 3. Enable accounts to use calendar 4. Tap on the sync option in Calendar EXPECTED: I expect it to update my calendar and notifications ACTUAL: In .cache/upstart/sync-monitor.log I see lots of error : error code from SyncEvolution remote, status 400: updateAllSubItems REPORT 'list items': bad HTTP status: status 1.1, code 400, class 4, Bad Request and error : error code from SyncEvolution remote, status 400: REPORT 'meta data': bad HTTP status: status 1.1, code 400, class 4, Bad Request and sync doesn't happen We are assuming this is a change on googles side that affects us on both vivid and rtm. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1438662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5
Having read several forums, I can say with little doubt that there's not a single BQ Aquaris user in France who receives MMS. It seems to be the same in Switzerland. I don't know about other countries. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1439101 Title: impossible receive MMS any operator on bq aquaris E4.5 Status in Messaging App: New Status in messaging-app package in Ubuntu: Confirmed Bug description: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1439101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442079] Re: Registry/ChildScopesRepository failures if some paths don't exist
** Changed in: unity-scopes-api (Ubuntu) Status: New = Fix Committed ** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) = Michi Henning (michihenning) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1442079 Title: Registry/ChildScopesRepository failures if some paths don't exist Status in unity-scopes-api package in Ubuntu: Fix Committed Bug description: I'm developing some tests in a clean linux container (much like a chroot), where I've never run a desktop session or our scopes. Because of that I've no ~/.local/share/applications directory, nor ~/.config /unity-scopes. This causes errors when scope registry attempts to create .desktop files and child scopes repository tries to store child-scopes.json. NB, it would be great if tests were not messing up with home directory contents; can it already be achieved with XDG_DATA_DIRS? scoperegistry [musicaggregator test]: ignoring scope mediascanner-music: cannot create metadata: unity::SyscallException: RegistryObject::create_desktop_file: unable to create desktop file: /home/vivid/.local/share/applications/mediascanner-music.desktop (errno = 2) scoperegistry [musicaggregator test]: ignoring scope mediascanner-video: cannot create metadata: unity::SyscallException: RegistryObject::create_desktop_file: unable to create desktop file: /home/vivid/.local/share/applications/mediascanner-video.desktop (errno = 2) scoperegistry [musicaggregator test]: ignoring scope musicaggregator: cannot create metadata: unity::SyscallException: RegistryObject::create_desktop_file: unable to create desktop file: /home/vivid/.local/share/applications/musicaggregator.desktop (errno = 2) scoperegistry [musicaggregator test]: ignoring scope videoaggregator: cannot create metadata: unity::SyscallException: RegistryObject::create_desktop_file: unable to create desktop file: /home/vivid/.local/share/applications/videoaggregator.desktop (errno = 2) scoperegistry [musicaggregator test]: no remote registry configured, only local scopes will be available scoperegistry [musicaggregator test]: ignoring installed scope musicaggregator: cannot create metadata: unity::SyscallException: RegistryObject::create_desktop_file: unable to create desktop file: /home/vivid/.local/share/applications/musicaggregator.desktop (errno = 2) [2015-04-09 12:31:20.129446] INFO: RegistryTest: ScopesWatcher: scope: musicaggregator installed to: /home/vivid/keywords/tests/data/../../src/musicaggregator scoperegistry [musicaggregator test]: ignoring installed scope mediascanner-music: cannot create metadata: unity::SyscallException: RegistryObject::create_desktop_file: unable to create desktop file: /home/vivid/.local/share/applications/mediascanner-music.desktop (errno = 2) [2015-04-09 12:31:20.130857] INFO: RegistryTest: ScopesWatcher: scope: mediascanner-music installed to: /home/vivid/keywords/tests/data/../../src/mymusic scoperegistry [musicaggregator test]: ignoring installed scope mediascanner-video: cannot create metadata: unity::SyscallException: RegistryObject::create_desktop_file: unable to create desktop file: /home/vivid/.local/share/applications/mediascanner-video.desktop (errno = 2) [2015-04-09 12:31:20.131932] INFO: RegistryTest: ScopesWatcher: scope: mediascanner-video installed to: /home/vivid/keywords/tests/data/../../src/myvideos scoperegistry [musicaggregator test]: ignoring installed scope videoaggregator: cannot create metadata: unity::SyscallException: RegistryObject::create_desktop_file: unable to create desktop file: /home/vivid/.local/share/applications/videoaggregator.desktop (errno = 2) [2015-04-09 12:31:20.133096] INFO: RegistryTest: ScopesWatcher: scope: videoaggregator installed to: /home/vivid/keywords/tests/data/../../src/videoaggregator [2015-04-09 12:31:20.193758] INFO: RegistryTest: RegistryObject::ScopeProcess::exec(): Process for scope: musicaggregator started [2015-04-09 12:31:20.197118] INFO: musicaggregator: ChildScopesRepository::read_repo(): Failed to open file: /home/vivid/.config/unity-scopes/musicaggregator/child-scopes.json [2015-04-09 12:31:20.197171] ERROR: musicaggregator: ChildScopesRepository::write_repo(): Failed to open file: /home/vivid/.config/unity-scopes/musicaggregator/child-scopes.json scoperunner: unity::ResourceException: Scope mediascanner-music: exception from start(): unable to open database file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1442079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421695] Re: Better offline mode in scopes
** Changed in: unity-scopes-api (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1421695 Title: Better offline mode in scopes Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Confirmed Bug description: Hi! An offline scope is empty. It'd be to have a reload button or the last online information. Please, see this video where I reproduce the issue: https://copy.com/mau3owb4cCofDUhQ Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1421695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422578] Re: segfault in QSearchQueryBase test
** Changed in: unity-scopes-api (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1422578 Title: segfault in QSearchQueryBase test Status in unity-scopes-api package in Ubuntu: Fix Released Bug description: Just got this on Jenkins CI for arm: The following tests FAILED: 82 - QSearchQueryBaseAPI (SEGFAULT) That's from the output at the end of the console log. The actual test run output is: test 82 Start 82: QSearchQueryBaseAPI 82: Test command: /tmp/buildd/unity-scopes-api-0.6.14+15.04.20150213bzr316pkg0vivid102/obj-arm-linux-gnueabihf/test/gtest/scopes/qt/qt-bindings/QSearchQueryBaseAPI_test 82: Test timeout computed to be: 1500 82: Running main() from gmock_main.cc 82: [==] Running 1 test from 1 test case. 82: [--] Global test environment set-up. 82: [--] 1 test from TestSetup 82: [ RUN ] TestSetup.bindings 82: SetUp() 82: Starting qt application 82: Thread id is: 0xb3a3b320 82: 82: GMOCK WARNING: 82: Uninteresting mock function call - returning default value. 82: Function call: event(0x803668) 82: Returns: false 82: Stack trace: 82/102 Test #82: QSearchQueryBaseAPI .***Exception: SegFault 0.60 sec Running main() from gmock_main.cc [==] Running 1 test from 1 test case. [--] Global test environment set-up. [--] 1 test from TestSetup [ RUN ] TestSetup.bindings SetUp() Starting qt application Thread id is: 0xb3a3b320 GMOCK WARNING: Uninteresting mock function call - returning default value. Function call: event(0x803668) Returns: false Stack trace: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1422578/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444872] Re: Empty-blank space when dragging icon to panel
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1444872 Title: Empty-blank space when dragging icon to panel Status in unity package in Ubuntu: Confirmed Bug description: Ubuntu 15.04 Vivid When dragging icon to panel it's become blank icon It's also happened in 14.04 LTS in unity (backport) from proposed repo. See this video https://www.youtube.com/watch?v=5mdWKA-vReU ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Apr 16 11:42:47 2015 InstallationDate: Installed on 2015-04-12 (3 days ago) InstallationMedia: 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/1444872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart
** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Pacemaker unable to communicate with corosync on restart + Pacemaker unable to communicate with corosync on restart under lxc -- 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/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc Status in lxc package in Ubuntu: New Status in pacemaker package in Ubuntu: Confirmed Bug description: We've seen this a few times with three node clusters, all running in LXC containers; pacemaker fails to restart correctly as it can't communicate with corosync, resulting in a down cluster. Rebooting the containers resolves the issue, so suspect some sort of bad state either in corosync or pacemaker. Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: mcp_read_config: Configured corosync to accept connections from group 115: Library error (2) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: main: Starting Pacemaker 1.1.10 (Build: 42f2063): generated-manpages agent-manpages ncurses libqb-logging libqb-ipc lha-fencing upstart nagios heartbeat corosync-native snmp libesmtp Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: cluster_connect_quorum: Quorum acquired Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1000 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1003 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: get_node_name: Defaulting to uname -n for the local corosync node name Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: crm_update_peer_state: pcmk_quorum_notification: Node juju-machine-4-lxc-4[1001] - state is now member (was (null)) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1003 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: crm_update_peer_state: pcmk_quorum_notification: Node (null)[1003] - state is now member (was (null)) Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: main: CRM Git Version: 42f2063 Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: get_node_name: Defaulting to uname -n for the local corosync node name Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync Apr 2 11:41:32 juju-machine-4-lxc-4 corosync[1033732]: [MAIN ] Denied connection attempt from 109:115 Apr 2 11:41:32 juju-machine-4-lxc-4 corosync[1033732]: [QB] Invalid IPC credentials (1033732-1033746). Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: cluster_connect_cpg: Could not connect to the Cluster Process Group API: 11 Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: main: HA Signon failed Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: main: Aborting startup Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]:error: pcmk_child_exit: Child process attrd (1033746) exited: Network is down (100) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: warning: pcmk_child_exit: Pacemaker child process attrd no longer wishes to be respawned. Shutting ourselves down. Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: pcmk_shutdown_worker: Shuting down Pacemaker Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: stop_child: Stopping crmd: Sent -15 to process 1033748 Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: warning: do_cib_control: Couldn't complete CIB registration 1 times... pause and retry Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: crm_shutdown: Requesting shutdown, upper limit is 120ms Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: warning: do_log: FSA: Input I_SHUTDOWN from crm_shutdown() received in state S_STARTING Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: do_state_transition: State transition S_STARTING - S_STOPPING [ input=I_SHUTDOWN cause=C_SHUTDOWN origin=crm_shutdown ] Apr 2 11:41:32 juju-machine-4-lxc-4 cib[1033743]:
[Touch-packages] [Bug 1401635] Re: NVIDIA driver makes internet very slow
Adrians Netlis, just to advise, you download the live environment from http://cdimage.ubuntu.com/daily-live/current/ , boot into it, and then run apport-collect in a terminal, as you previously did following https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1401635/comments/1 . -- 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/1401635 Title: NVIDIA driver makes internet very slow Status in xorg package in Ubuntu: Expired Bug description: Here is information about bug: I am not a good computer spec, so I could not find reason of it, but, when I installed NVIDIA bin-331.89 driver from additional drivers, it appeared a bug so my internet became very slow. I use Realtek RTL8111/RTL8168... ethernet adapter. I have r8169 kernel driver in use(I am not allowed to modify internet stuff in this computer, cause this is actually my parent's PC). Wehn I installed NVIDIA driver, internet appeared to work very, very slow. After getting rid of it, it became nice again. Could you, please, look trought this and find something to fix this. Maybe you could gimme full tutorial on how to do it if I have: 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2014-12-01 17:54:03,868 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Gainward GeForce GT 610 [10b0:104a] InstallationDate: Installed on 2014-11-26 (17 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=2e2221b2-b6c7-4553-815f-67afdc924a98 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-12-01 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: H61M-VG3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-VG3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Dec 13 10:47:27 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPIXART USB OPTICAL MOUSE MOUSE, id 8 inputUSB USB Keykoard KEYBOARD, id 9 inputUSB USB Keykoard KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2 xserver.video_driver: nouveau To manage notifications about this bug go to:
[Touch-packages] [Bug 1444883] [NEW] Emergency numbers for China (110, 119) are not available in emergency mode
Public bug reported: arale device, r177, ubuntu-touch/vivid-proposed Steps 1. Emergency mode (e.g. Lock phone with a passcode, slide left, tap on Emergency Call) 2. try input 911, 112 == OK 2. try input 110, 119 == Dial button is inactive after number is input Expect Allow these numbers in emergency mode ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- 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/1444883 Title: Emergency numbers for China (110,119) are not available in emergency mode Status in dialer-app package in Ubuntu: New Bug description: arale device, r177, ubuntu-touch/vivid-proposed Steps 1. Emergency mode (e.g. Lock phone with a passcode, slide left, tap on Emergency Call) 2. try input 911, 112 == OK 2. try input 110, 119 == Dial button is inactive after number is input Expect Allow these numbers in emergency mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1444883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443019] Re: renderer process is killed on image-heavy pages on krillin
So when the page becomes blank, that means that the system killed the renderer process because it considered that it was using too much memory. When that happens, could you grep for 'oxide-renderer' in /var/log/syslog, and paste the relevant section (see comment #1 in this report for how it looks like). Information about the pages you were browsing (if it’s not confidential) would be helpful, as well as whether you were running many apps (particularly webapps that use the oxide renderer process too). Thanks! -- 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/1443019 Title: renderer process is killed on image-heavy pages on krillin Status in Oxide Webview: New Status in Web Browser App: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: On the BQ ubuntu phone, while browsing image-heavy pages, the browser suddenly turns completely white and unresponsive. Closing the app and restarting it fixes the problem. example: I can't watch this page to the end, because the browser crashes in the middle... https://imgur.com/gallery/NnGyq I have this on a lot of websites, after browsing for 30 minutes, the browser crashes... To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1443019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
Any chance of a _very_ hand-holdy description of how to fix this? I ran into the issue yesterday with my Aquaris phone (obviously the updated image hasn't landed on the phones yet) and, as the original submitter says, now have an effectively bricked phone (although the alarm woke me up this morning:-). The workaround described in comment 4 is simply not detailed enough for me to understand what I need to do (or the risks associated with it). In many ways I'd be more comfortable using some kind of press these hardware buttons in this combination to reset settings to default kind of option (if that exists and won't also result in my data being wiped). For the record, my phone was AFAIK up to date in terms of OTA updates (as in, yesterday lunchtime I'd updated the OS and apps). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1256196] Re: zeitgeist-fts uses a lot of memory (more than 200MB)
I can easily get over 1.0 gb after I click on the Ubuntu Dash (my personal record was 1.8 gb, and considering that I'm using just 2gb of RAM that's not a pleasant thing). 14.10 too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1256196 Title: zeitgeist-fts uses a lot of memory (more than 200MB) Status in zeitgeist package in Ubuntu: Confirmed Bug description: Hi, I find that zeitgeist-fts process uses continuously a lot of memory between 10 and 20% of a 2GB laptop. See the attached screenshot. Is it a normal behavior ? I can provide the activity file if required. Nicolas ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: zeitgeist-core 0.9.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic i686 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: i386 Date: Fri Nov 29 09:37:44 2013 EcryptfsInUse: Yes ExecutablePath: /usr/lib/zeitgeist/zeitgeist-fts InstallationDate: Installed on 2013-06-10 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: zeitgeist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1256196/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444880] [NEW] xrandr report inverted gamma values
Public bug reported: $ xrandr --output VGA1 --gamma 1:1:1.7 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 Gamma: 1.0:1.0:0.59 Brightness: 1.0 $ xrandr --output VGA1 --gamma 1:1:.6 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 Gamma: 1.0:1.0:1.7 Brightness: 1.0 As you can see in output of commands above, Gamma values printed by xrandr --verbose are exactly the invert of the values set: 1/value set... Appart for value 1.0 which is correct. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Description changed: $ xrandr --output VGA1 --gamma 1:1:1.7 $ xrandr --verbose | grep -iE '(gamma|bright)' - Gamma: 1.0:1.0:1.7 - Brightness: 1.0 - Gamma: 1.0:1.0:0.59 - Brightness: 1.0 + Gamma: 1.0:1.0:1.7 + Brightness: 1.0 + Gamma: 1.0:1.0:0.59 + Brightness: 1.0 $ xrandr --output VGA1 --gamma 1:1:.6 $ xrandr --verbose | grep -iE '(gamma|bright)' - Gamma: 1.0:1.0:1.7 - Brightness: 1.0 - Gamma: 1.0:1.0:1.7 - Brightness: 1.0 + Gamma: 1.0:1.0:1.7 + Brightness: 1.0 + Gamma: 1.0:1.0:1.7 + Brightness: 1.0 - As you can see, Gamma values printed by xrandr --verbose are exactly - 1/value set... + As you can see in output of commands above, Gamma values printed by + xrandr --verbose are exactly the invert of the values set: 1/value + set... ** Description changed: $ xrandr --output VGA1 --gamma 1:1:1.7 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 Gamma: 1.0:1.0:0.59 Brightness: 1.0 $ xrandr --output VGA1 --gamma 1:1:.6 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 Gamma: 1.0:1.0:1.7 Brightness: 1.0 As you can see in output of commands above, Gamma values printed by xrandr --verbose are exactly the invert of the values set: 1/value - set... + set... Appart for value 1.0 which is correct. -- 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/1444880 Title: xrandr report inverted gamma values Status in xorg package in Ubuntu: New Bug description: $ xrandr --output VGA1 --gamma 1:1:1.7 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 Gamma: 1.0:1.0:0.59 Brightness: 1.0 $ xrandr --output VGA1 --gamma 1:1:.6 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 Gamma: 1.0:1.0:1.7 Brightness: 1.0 As you can see in output of commands above, Gamma values printed by xrandr --verbose are exactly the invert of the values set: 1/value set... Appart for value 1.0 which is correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444880/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441449] Re: [HP Z820] external microphone does not work, only records noises
** Changed in: hwe-next Assignee: (unassigned) = Keng-Yu Lin (lexical) ** Changed in: hwe-next Importance: Undecided = Critical ** Changed in: hwe-next 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/1441449 Title: [HP Z820] external microphone does not work, only records noises Status in HWE Next Project: Incomplete Status in alsa-driver package in Ubuntu: Confirmed Bug description: Records with a lot noises, barely can heard the sound. Step to reproduce: 1. plug your microphone to the front/rear micrphone jack 2. turn up the microphone volume in the system sound settings 3. open a terminal then type command: arecord test.wav, ctrl-c to inturrupt when you finish Expected result: when playing the recordings it should plays recognizable sound. Actual results: A lot noise in the recordings. Additional information: In the attached recording file, you should hear, Testing, One, Two, Three, Four, Five . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1696 F pulseaudio /dev/snd/controlC0: ubuntu 1696 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 8 01:32:46 2015 InstallationDate: Installed on 2015-04-02 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J63 v03.69 dmi.board.asset.tag: 2UA4242K12 dmi.board.name: 158B dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.01 dmi.chassis.asset.tag: 2UA4242K12 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ63v03.69:bd03/25/2014:svnHewlett-Packard:pnHPZ820Workstation:pvr:rvnHewlett-Packard:rn158B:rvr1.01:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Z820 Workstation dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1441449/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352408] Re: [OOBE] Edge demo lets you swipe from the left in the Swipe from the right screen
** Changed in: ubuntu-ux Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1352408 Title: [OOBE] Edge demo lets you swipe from the left in the Swipe from the right screen Status in Ubuntu UX bugs: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: In all the screens of the edge demo we are taught how to use one border, so we learn we can use them all. Except in the Swipe from the right screen where you can also swipe from the left. I find this confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1352408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
That info seemed to belong on askubuntu: http://askubuntu.com/questions/609938/how-do-i-factory-reset-a-bq- aquaris-e4-5-ubuntu-edition-from-the-handset -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443319] Re: when you close a maximized window, you will never see close-minimized-maximizedbutton anymore
** Branch linked: lp:~huangzhiquan/unity8/windowcontrolbutton -- 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/1443319 Title: when you close a maximized window,you will never see close-minimized- maximizedbutton anymore Status in unity8 package in Ubuntu: New Bug description: step: 1.open an app(like note-app,whatever) 2.maximized the window of note-app 3.close it 4.open note-app except: we will see close-minimized-maximized button actually: we will not see these To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1443319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397685] Re: git gnutls_handshake() failed: A TLS packet with unexpected length was received.
There are several issues with TLS connections and the F5 firewall, and that looks like the case. That firewall terminates a TLS session if the client hello is between 256 and 512 bytes. If that is the case you can verify using wireshark. The solution we adopted in later versions of gnutls is to add padding: https://gitlab.com/gnutls/gnutls/commit/b6d29bb1737f96ac44a8ef9cc9fe7f9837e20465 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnutls26 in Ubuntu. https://bugs.launchpad.net/bugs/1397685 Title: git gnutls_handshake() failed: A TLS packet with unexpected length was received. Status in git package in Ubuntu: New Status in gnutls26 package in Ubuntu: New Status in gnutls28 package in Ubuntu: New Bug description: Platform: Ubuntu 14.04, ppc64le (Power 8 LE), git version: 1:1.9.1-1 When accessing a public repository over HTTPS, I get the following error: $ git clone --no-checkout https://git.fedorahosted.org/git/lvm2.git lvm2 Cloning into 'lvm2'... fatal: unable to access 'https://git.fedorahosted.org/git/lvm2.git/': gnutls_handshake() failed: A TLS packet with unexpected length was received. Accessing the same public repository from a different machine running in a different network - also Ubuntu 14.04, but running on x86-64, the commands executed with no errors. Both platforms have the same git version (dpkg -l | grep git) I checked online for an explanation. Found this: http://askubuntu.com/questions/186847/error-gnutls-handshake-falied-when-connecting-to-https-servers According to that, Gnu TLS may have some issues when proxies (firewalls?) are present on the network path to the repositories. The recommended solution is to rebuild git using OpenSSL instead of TLS. I tried it and got to a different error (Unknown SSL protocol error). Can you please fix git to make it work correctly? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/1397685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441796] Re: Harness constantly prints boost::filesystem errors and sometimes aborts
Rodney, did the branch fix the problem for you? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1441796 Title: Harness constantly prints boost::filesystem errors and sometimes aborts Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: terminate called after throwing an instance of 'boost::filesystem::filesystem_error' what(): boost::filesystem::equivalent: No such file or directory: /tmp/tmpvb08fgci/.local/share/unity-scopes/unconfined/client/logs, /tmp/tmp9ha9gfc6/.local/share/unity-scopes/unconfined/client/logs scoperegistry: no remote registry configured, only local scopes will be available Aborted When running the tests locally, many similar messages to this are repeated, but often without aborting. On the jenkins armhf builder, it seems to cause an abort fairly consistently, due to this unhandled exception. This also causes the python3 process to hang, which causes further errors to show up in the logs, as the chroot apparently cannot unmount /run/shm when this happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1441796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
@John -- thanks very much for the feedback. One question: what does the wipe cache partition option mean (as opposed to the factory reset, which is obvious)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442550] Re: Documentation missing return values
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- 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/1442550 Title: Documentation missing return values Status in Content sharing/picking infrastructure and service: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Many of the methods in the documentation are missing return values. This makes them really hard to read: https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.AbstractButton/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Action/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ActionItem/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Alarm/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Button/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.CheckBox/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Clipboard/ (one correct, 2 missing) https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.PageStack/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Panel/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.PickerPanel/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Slider/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.TextArea/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.TextField/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ToolbarButton/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ListItems.Empty/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.ListItems.ExpandablesColumn/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Pickers.Picker/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Pickers.PickerDelegate/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Popups.Popover/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.Popups.PopupBase/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Test.TestExtras/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Test.UbuntuTestCase/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Content.ContentPeer/ https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Content.ContentTransfer/ Here's an example of a correct one: https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.Components.AlarmModel/ To manage notifications about this bug go to: https://bugs.launchpad.net/content-hub/+bug/1442550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421060] Re: Boost log uses all inodes if file system is full
** Changed in: unity-scopes-api (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1421060 Title: Boost log uses all inodes if file system is full Status in the base for Ubuntu mobile products: Fix Committed Status in unity-scopes-api package in Ubuntu: Fix Released Bug description: boost::log, if file rotation happens while the file system is full, creates hundreds of empty log files per log directory, eventually consuming all available inodes. But reported here: https://svn.boost.org/trac/boost/ticket/11016 We need to track this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444872] [NEW] Empty-blank space when dragging icon to panel
Public bug reported: Ubuntu 15.04 Vivid When dragging icon to panel it's become blank icon It's also happened in 14.04 LTS in unity (backport) from proposed repo. See this video https://www.youtube.com/watch?v=5mdWKA-vReU ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Apr 16 11:42:47 2015 InstallationDate: Installed on 2015-04-12 (3 days ago) InstallationMedia: SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug trusty unity vivid -- 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/1444872 Title: Empty-blank space when dragging icon to panel Status in unity package in Ubuntu: New Bug description: Ubuntu 15.04 Vivid When dragging icon to panel it's become blank icon It's also happened in 14.04 LTS in unity (backport) from proposed repo. See this video https://www.youtube.com/watch?v=5mdWKA-vReU ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Apr 16 11:42:47 2015 InstallationDate: Installed on 2015-04-12 (3 days ago) InstallationMedia: 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/1444872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444895] [NEW] xrandr --brightness resets gamma ratio
Public bug reported: $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 $ xrandr --output VGA1 --brightness .75 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.0 Brightness: 0.75 As can be seen in the above command output, changing the brightness with xrandr resets the gamma ratio to 1/1/1/ instead of 1/1/.6 (values in xrandr --verbose output are inverted...) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1444895 Title: xrandr --brightness resets gamma ratio Status in xorg package in Ubuntu: New Bug description: $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.7 Brightness: 1.0 $ xrandr --output VGA1 --brightness .75 $ xrandr --verbose | grep -iE '(gamma|bright)' Gamma: 1.0:1.0:1.0 Brightness: 0.75 As can be seen in the above command output, changing the brightness with xrandr resets the gamma ratio to 1/1/1/ instead of 1/1/.6 (values in xrandr --verbose output are inverted...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1444895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365728] Re: SRU: pyvenv fails due to mising ensurepip module
*** This bug is a duplicate of bug 1348954 *** https://bugs.launchpad.net/bugs/1348954 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3.4 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1365728 Title: SRU: pyvenv fails due to mising ensurepip module Status in python3.4 package in Ubuntu: Confirmed Bug description: [Impact] * Anyone attempting to use the pyenv script from Python 3.4 will be met with a fairly confusing error by default. This would have worked fine in saucy and raring. * While this can be worked around by adding a flag to the pyvenv script, it also removes the ability to have pip installed into a pyvenv virtualenv at all. This will prevent people from using one of the new features that comes with Python 3.4. * This should be backported to the stable release because it is a major regression in Python 3's pyvenv from previous Ubuntu releases. Additionally it removes one of the documented features of Python 3.4. [Test Case] * This can be reproduced just by doing ``python3.4 -m venv /any/tmp/path``. You will get an error that says something like: Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 [Regression Potential] * I believe that the primary risk for regression will be within the python(3)-pip packages. This is because the patches that fixed this changed the build process there. I do not however believe that there will be any subtle or non obvious regressions (if any at all). [Other Info] * The original bug for this can be found at https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1290847 * This regression comes from the fact that in Python 3.4 an additonal module was added to the stdlib, called ensurepip, that shipped a binary package (a Wheel) of pip. This allowed Python to include a command (python -m ensurepip) which would bootstrap an installation of pip into the current environment. The venv module was then modified to use this to install a copy of pip into the new virtual environment. The Python package was patched to rm -rf the ensurepip module during the install breaking the venv module in the process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1365728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432413] Re: Synaptic Touchpad xevents are hijacked under X
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- 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/1432413 Title: Synaptic Touchpad xevents are hijacked under X Status in xorg package in Ubuntu: Confirmed Bug description: Synaptic Touchpad xevents are hijacked under X11. I have a problem with the synaptic touch-pad on my Acer Aspire that started around a week ago. The problem can be described as that there is a massive amount of xevents being generated and appearing to originate from the touch-pad even though the touch-pad is not used. I have tested the HW which seems to work fine. The test performed is to start a terminal session (Ctrl + Alt + 2) before the fault occurs and check the xevents by running ~$ sudo evtest /dev/input/eventX where the X to use is found in /proc/bus/input/devices and found by running ~$ cat /proc/bus/input/devices |grep mouse No matter how much the touch-pad is used will the console show the corresponding events which indicates that HW and driver works OK as long it is not under X When the problem has occurred (in Desktop mode) is it easy (but inconvenient) to get back to normal by key combo Fn+F7 twice, turn off touch-pad and then turn on again. And more, one can get unlucky in the sense that the generated events could click somewhere one do not want to click. During the problem is it impossible to use the mouse since it flies around (mostly going in a bottom to top of screen direction) but one can check the generated events using evtest again. How can I help troubleshooting the problem? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 19:51:13 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0933] InstallationDate: Installed on 2015-02-21 (22 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Acer Aspire E3-112 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=a97d0b51-4244-48ca-ba87-bc3a38a8b62d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-112 dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Mar 15 18:59:07 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1576 vendor BOE xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
I've being trying to reproduce this under KVM and on hardware (no LXC) but I'm unable to reproduce the problem, so this appears isolated to LXC. The pacemaker - corosync communication occurs over IPC implemented using shared memory. I'm wondering whether this is managing to get into an inconsistent state. The other thing worth noting is that in the deployment impacted, there are multiple corosync/pacemaker clusters running on the same physical host, but under different LXC containers. -- 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/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc Status in lxc package in Ubuntu: New Status in pacemaker package in Ubuntu: Confirmed Bug description: We've seen this a few times with three node clusters, all running in LXC containers; pacemaker fails to restart correctly as it can't communicate with corosync, resulting in a down cluster. Rebooting the containers resolves the issue, so suspect some sort of bad state either in corosync or pacemaker. Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: mcp_read_config: Configured corosync to accept connections from group 115: Library error (2) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: main: Starting Pacemaker 1.1.10 (Build: 42f2063): generated-manpages agent-manpages ncurses libqb-logging libqb-ipc lha-fencing upstart nagios heartbeat corosync-native snmp libesmtp Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: cluster_connect_quorum: Quorum acquired Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1000 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1003 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: get_node_name: Defaulting to uname -n for the local corosync node name Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: crm_update_peer_state: pcmk_quorum_notification: Node juju-machine-4-lxc-4[1001] - state is now member (was (null)) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1003 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: crm_update_peer_state: pcmk_quorum_notification: Node (null)[1003] - state is now member (was (null)) Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: main: CRM Git Version: 42f2063 Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: get_node_name: Defaulting to uname -n for the local corosync node name Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync Apr 2 11:41:32 juju-machine-4-lxc-4 corosync[1033732]: [MAIN ] Denied connection attempt from 109:115 Apr 2 11:41:32 juju-machine-4-lxc-4 corosync[1033732]: [QB] Invalid IPC credentials (1033732-1033746). Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: cluster_connect_cpg: Could not connect to the Cluster Process Group API: 11 Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: main: HA Signon failed Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: main: Aborting startup Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]:error: pcmk_child_exit: Child process attrd (1033746) exited: Network is down (100) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: warning: pcmk_child_exit: Pacemaker child process attrd no longer wishes to be respawned. Shutting ourselves down. Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: pcmk_shutdown_worker: Shuting down Pacemaker Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: stop_child: Stopping crmd: Sent -15 to process 1033748 Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: warning: do_cib_control: Couldn't complete CIB registration 1 times... pause and retry Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: crm_shutdown: Requesting shutdown, upper limit is 120ms Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: warning: do_log: FSA: Input I_SHUTDOWN from crm_shutdown()
[Touch-packages] [Bug 1425544] Re: Aggregator scopes must not forward location setting to scopes
** Changed in: unity-scopes-api (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1425544 Title: Aggregator scopes must not forward location setting to scopes Status in unity-scopes-api package in Ubuntu: Fix Released Bug description: If a user explicitly denies location to a specific scope, then the scope should never ever receive location data even though a possible aggregator scope got location data granted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1425544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444937] Re: QML cache gets stale too easily
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1444937 Title: QML cache gets stale too easily Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: It's happened many times now that after looking for an issue the source of it ended up to be stale QML cache. We need the cache to be cleared more aggressively, likely on any QML- related package installation. App-specific cache should be (if it's not) cleared on install (or maybe better - removal) and upgrade. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libqt5qml5 5.4.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 12:25:21 2015 SourcePackage: qtdeclarative-opensource-src SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1444937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401635] Re: NVIDIA driver makes internet very slow
Is the Live Environment requiered? And which one is the one? I don't think my parents are going to allow me to do it! -- 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/1401635 Title: NVIDIA driver makes internet very slow Status in xorg package in Ubuntu: Expired Bug description: Here is information about bug: I am not a good computer spec, so I could not find reason of it, but, when I installed NVIDIA bin-331.89 driver from additional drivers, it appeared a bug so my internet became very slow. I use Realtek RTL8111/RTL8168... ethernet adapter. I have r8169 kernel driver in use(I am not allowed to modify internet stuff in this computer, cause this is actually my parent's PC). Wehn I installed NVIDIA driver, internet appeared to work very, very slow. After getting rid of it, it became nice again. Could you, please, look trought this and find something to fix this. Maybe you could gimme full tutorial on how to do it if I have: 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2014-12-01 17:54:03,868 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Gainward GeForce GT 610 [10b0:104a] InstallationDate: Installed on 2014-11-26 (17 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=2e2221b2-b6c7-4553-815f-67afdc924a98 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-12-01 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: H61M-VG3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-VG3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Dec 13 10:47:27 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPIXART USB OPTICAL MOUSE MOUSE, id 8 inputUSB USB Keykoard KEYBOARD, id 9 inputUSB USB Keykoard KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1401635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1444946] [NEW] no launchpad, dash, just background on desktop
Public bug reported: I can run Ubuntu 14.10 from the live dvd. i installed this same os and it worked a few times. now, every time i turn off my laptop and boot up the os i get a blank screen with no dash, launchpad, nothing. I haven't found a solution to this in 14.10, but i tried the solutions with the older os. example: sudo apt-get update sudo apt-get install --reinstall ubuntu Desktop sudo apt-get instal unity sudo shutdown -r now also: rm rf.compiz-1 (this did nothing, so i changed the command to the following) rm -r -f compiz-1 (this would work for that session, but when i shut down my computer and booted it back up i would get the same problem, no dash, launchpad, just blank screen.) i tried the same command in the terminal (rm -r -f compiz-1) and it would work for that session. this temporary fix worked a few times, then it stopped working and i went back to no dash, just blank screen. i also tried: sudo apt-get install compizconfig-settings-manager Display =:0 ccsm this got me to the unity manager. the unity plugin was already enabled. i rebooted and i had the dash. after i shutdown and booted up the os later, i had no dash, just plain background. i finally went and downloaded linuxmint 17.1 running it from the live dvd and i had the same problem, just the background with no dash. i'm new to linux so i am only doing commands from what i see at :askubuntu.com also, i think i have a man-in-the-middle attack. i tried to set up privatetunnel with no success. my system is an old toshiba laptop satellite with 80 GB of HDD and 2 GB RAM. i know ubuntu 15.04 is coming out this month and i will definetly try that. I want to stay with linux so any help with this problem will be appreciated. I'm currently running from the live dvd and i will again try to reinstall ubuntu 14.10 and if i get the dash i will leave my computer on so i don't loose it, or until i can get a permanent fix for this issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CasperVersion: 1.345 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Apr 16 09:40:41 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff02] Subsystem: Toshiba America Info Systems Device [1179:ff02] LiveMediaBuild: Ubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) MachineType: TOSHIBA * PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.50 dmi.board.name: IAKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.50:bd05/21/2007:svnTOSHIBA:pn*:pvrPSAD0U-0N700P:rvnTOSHIBA:rnIAKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: * dmi.product.version: PSAD0U-0N700P dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Apr 16 08:55:04 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40972 vendor DEL xserver.version: 2:1.16.0-1ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubuntu utopic -- 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/1444946 Title: no launchpad, dash, just background on desktop Status in xorg package in Ubuntu:
[Touch-packages] [Bug 953875] Re: Encrypted swap no longer mounted at bootup
** Bug watch added: Debian Bug tracker #751707 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751707 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751707 Importance: Unknown Status: Unknown ** Bug watch added: freedesktop.org Bugzilla #87717 https://bugs.freedesktop.org/show_bug.cgi?id=87717 ** Also affects: systemd via https://bugs.freedesktop.org/show_bug.cgi?id=87717 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu Vivid) Importance: Undecided = High -- 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/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Unknown Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: In Progress Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Unknown Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log
[Touch-packages] [Bug 1302955] Re: upstart user session leaks all the dbus events it receives
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1302955 Title: upstart user session leaks all the dbus events it receives Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in unity source package in Trusty: Fix Released Bug description: [Impact] The unity-panel-service process has been caching D-Bus messages sent from upstart, effectively leaking memory. The solution replaces the offending code with a single upstart event emission. [Test Case] 0. Make sure there is a user session job with a dbus rule (eg unity-greeter-session-broadcast) 1. Install and run system-load-indicator (indicator-multiload) 2. Set the update interval to 100ms 3. Now watch the memory use of init --user increase by 100kb per second 4. Also open up upstart-monitor to see all the dbus messages being sent [Regression Potential] Some kind of hidden functionality depending on upstart events sent through D-Bus to the unity-panel-service may have become disconnected. Unlikely. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in regular use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390562] Re: Moving the mouse out from the decoration hides the LIMs when Alt is pressed
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390562 Title: Moving the mouse out from the decoration hides the LIMs when Alt is pressed Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] Pressing the Alt key while a locally integrated menu is open causes the menu to hide. [Test Case] Prerequisite: from Appearance - Behavior - Set menu visible in window titlebar 1. Open a window with menus 2. Press and keep pressed the Alt key 3. Menus will show 4. Move the mouse over the window decoration 5. Move the mouse out from the window decoration Incorrect behavior: 6. Menus hides, also if the Alt key is pressed. Expected: 6. Menus should stay visible until the Alt key is released. [Regression Potential] Additional incorrect menu behaviour may be introduced. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1390562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312137] Re: Local menus broken for Qt apps after opening dialog
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1312137 Title: Local menus broken for Qt apps after opening dialog Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] I have selected to have window menus in the window's title bar. This works great, except for Qt apps. After selecting a menu item in a Qt app that produces a dialog, the menu is no longer accessible. The only way to get the menu back, is to switch to another window, and then back to the affected app. [Test Case] 1. Start qtcreator 2. Resize window so that it is not maximised 3. Select 'Help' - 'About Qt Creator' 4. Dismiss 'About Qt Creator' dialog 5. Move mouse over window titlebar. [Regression Potential] It's possible other menu interaction bugs may have been introduced. [Other Info] The fix for Ubuntu 14.04 LTS was cherry-picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1312137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404486] Re: Session dialog does not show up over fullscreen windows.
** Changed in: unity/7.2 Status: In Progress = Fix Committed ** Changed in: unity Status: Triaged = Fix Released -- 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/1404486 Title: Session dialog does not show up over fullscreen windows. Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [IMPACT] Unity session dialog does not show up over a fullscreen window if you press the hardware button. [TEST CASE] (1) open an application (eg. Firefix) and make it fullscreen (F11) (2) press the power button or choose Shut Down... from the Session indicator menu. (3) The Session (shutdown/restart) dialog should appear and be interactive. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1404486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401911] Re: When the screen is locked edge barriers should be deactivated.
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1401911 Title: When the screen is locked edge barriers should be deactivated. Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] If the screen is locked, launcher/panel edge barriers at the moment are active. [Test Case] In a multi-monitor environment, lock the screen and move the mouse between monitors. There should be no sticky edge between the monitors. [Regression Potential] Code in the paths that handle the edge barriers was changed. Potentially this could impact the reveal of a hidden Launcher if there were errors introduced in these code paths. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1401911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1241757] Re: Unity Launcher always assumes default background is active for a couple of seconds
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1241757 Title: Unity Launcher always assumes default background is active for a couple of seconds Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [IMPACT] Every time the computer boots and autologins to my desktop, I see the default background only behind the Unity Launcher for a couple of seconds, and then it is replaced with the current wallpaper. [TEST CASE] (1) Configure the desktop to use a non-default wallpaper. (2) Log in to a Unity session and observe the area behind the Launcher. [REGRESSION POTENTIAL] The solution to this problem was to eliminate the animation of the BFB icon on initial startup. Potentially this could cause the animation to not run at other times, although even if this did occur, it is unlikely to be noticed. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1241757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374942] Re: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1374942 Title: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] An invalid line of code would occasionally cause Unity to crash. [Test Case] (1) Download and run the attached Python script test-1374942 to create a candidate application. (2) Press the close button and wait for the Force Quit dialog to come up. (3) Choose the Force Quit button. The desktop shell should not crash. [Regression Potential] The fix for this bug involves converting an integer into a string and appending it to an error message instead of adding the integer value to the address of the error message. There is unlikely to be a regression from this. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been under daily use for some time without apparent regressioon. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1374942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1398287 Title: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] When the power button is pressed, the shutdown dialog will be displayed. Then clicks the 'Lock' button in the shutdown dialog and it sometimes takes about 30~60s to lock screen. This happens on many Intel-only platforms. PS: If user moves the cursor out of the dialog window after clicking the 'Lock' button, it will switch to lock screen immediately. [Test Case] See description under Impact' above. [Regression Potential] The fix for this problem involves releasing the grab on the input devices earlier in the sequence, allowing the animation sequence to begin immediately without a grab-release timeout. It is unlikely that this could introduce any regressions. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivid Vervet dev release where it has been in test for some time without incident. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] Certain code paths may cause the Unity lockscreen to crash, which can allow the screen to be unlocked without a password entry. [Test Case] Unfortunately this bug only appears under certain race conditions and is not reliably reproduce able. [Regression Potential] The change in the code simply assumes that if a screen is already locked, then it is lockable this avoiding certain operations that are inherently racy. It is possible that this fix does not avoid all possible crash conditions in the lockscreen and there may still be unaccounted-for crashes in the lockscreen. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivid Vervet dev release where it has been in testing for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363534] Re: Wrong keyboard shortcuts for Workspaces in Dash overlay
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1363534 Title: Wrong keyboard shortcuts for Workspaces in Dash overlay Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] The Shortcuts displays the wrong key sequence for switching workspaces. [Test Case] (1) Enable workspaces (System Settings Appearance Behavior Enable Workspaces). (2) Hold down the Super key until the Shortcuts window appears. (3) Under Workspaces it should display Shift + Ctrl + Alt + Arrow Keys and not Shift + Ctrl + Alt + Left + Arrow Keys. [Regression Potential] Unlikely. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu Vivi Vervet dev release where it has been in production use for some time without regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363534/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1159249] Re: HUD does not show up over fullscreen window
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1159249 Title: HUD does not show up over fullscreen window Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] The HUD was not being rendered above fullscreen windows although it would grab the keyboard. [TEST CASE] 1. Open some site in firefox 2. Go to fullscreen mode (F11) 3. Press Alt once. 4 The HUD should appear and you should be able to interact with it. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1159249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 860970] Re: Dash called with super key above fullscreen app is not interactive or does not show up at all.
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/860970 Title: Dash called with super key above fullscreen app is not interactive or does not show up at all. Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: Won't Fix Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Precise: Triaged Status in unity source package in Trusty: Fix Released Bug description: [IMPACT] The Dash was rendered underneath fullscreen windows so it was invisible, although it grabs keyboard input. [TEST CASE] - Launch an application in fullscreen (Firefox, Totem). - Hit the Super key to call the dash. - The Dash should appear. - Keyboard input should be directed to the Dash. - Clicking anywhere on the full screen application should close the Dash. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/860970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 955193] Re: Menu bar - add option for the global menu to make it always visible
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/955193 Title: Menu bar - add option for the global menu to make it always visible Status in Ayatana Design: Triaged Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [ Impact ] [Test Case] (1) enable menus in the window title bar System Settings Appearance Behavior Show the menus for a window In the menu bar (2) run gsettings set com.canonical.Unity always-show-menus true in a terminal (3) move the mouse around between windows The menus should remain displayed [Regression Potential] Any change to the menu functionality has the potential to cause volunteer functionality in menu behaviour. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time with no apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/955193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 953875] Re: Encrypted swap no longer mounted at bootup
systemd fix sent upstream and committed to Debian experimental branch. ** Changed in: systemd (Ubuntu Vivid) Milestone: None = ubuntu-15.04 ** Changed in: systemd (Ubuntu Vivid) Status: In Progress = Fix Committed -- 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/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Unknown Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Committed Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Unknown Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
I solved this problem by installing the xserver-xorg. Quad-Core Intel® Core™ i5-4210U CPU @ 1.70GHz Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Linux-Kernel-Headers - Headers Files for the Linux Kernel: New Status in Mesa: New Status in Ubuntu UX bugs: New Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 953875] Re: Encrypted swap no longer mounted at bootup
** Changed in: systemd (Debian) Status: Unknown = Confirmed -- 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/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Unknown Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Committed Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Confirmed Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1. - Edit /etc/crypttab to append ,offset=1024 in the fourth (last) column of the cryptswap1 line; ensure that there is *no space* between the cipher=aes-cbc-essiv:sha256 and the appended option. If there is a leading # in the file, remove that too. - If there is a leading # in /etc/fstab in the line starting with /dev/mapper/cryptswap1 line, remove that. - Run sudo update-initramfs -u. ORIGINAL REPORT === Clean install of 12.04 and with encrypted home for my user. Did all updates and now the bootup hangs waiting for swap to become available and it never seems to ever finish. The 200GB SSD below is my boot drive and root filesystem. alan@mesh:~$ sudo swapon -a [sudo] password for alan: swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory alan@mesh:~$ grep swap /etc/fstab # swap was on /dev/sdg5 during installation #UUID=22d3f7f0-f715-4582-81ba-dcbd4cdd1495 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 alan@mesh:~$ sudo fdisk -l Disk /dev/sda: 115.0 GB, 115033153536 bytes 255 heads, 63 sectors/track, 13985 cylinders, total 224674128 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000ba2ed Device Boot Start End Blocks Id System /dev/sda1 *2048 206847 1024007 HPFS/NTFS/exFAT /dev/sda2 206848 224671743 1122324487 HPFS/NTFS/exFAT Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf0fa0806 Device Boot Start End Blocks Id System /dev/sdb12048 349304831 1746513927 HPFS/NTFS/exFAT /dev/sdb2 374722558 390721535 79994895 Extended /dev/sdb3 * 349304832 37472051112707840 83 Linux /dev/sdb5 374722560 390721535 7999488 82 Linux swap / Solaris Partition table entries are not in disk order ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libecryptfs0 96-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 13 09:56:56 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120215) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ecryptfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429899] Re: StateSaver should not restore when app launched from content-hub
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/statesaver-vs-urihandler -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1429899 Title: StateSaver should not restore when app launched from content-hub Status in content-hub package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Testing the messaging-app state saving ability that we've been adding from this MR: https://code.launchpad.net/~tiagosh/messaging-app/state-saver2/+merge/250996 deb can be found here: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/1669/artifact/work/output/*zip*/output.zip The problem is, when the app is launched from the content-hub, the StateSaver still tries to restore it's previously saved state, but it should not and this causes problems. It should clear the state, the same way it does when launched via url-dispatcher. According to Ken, there are content-hub signals that StateSaver will need to listen to in order to know when the app is being launched by content-hub. To reproucde: 1) install the messaging-app deb from above 2) open messaging-app, swipe from bottom to create a new message 3) type some names in the recipient field, and type some message in the send field 4) do kill -2 pidOfMessagingApp to kill the messaging-app and save it's state 5) open camera-app and go to the photo roll 6) press Share from toolbar and select messaging-app from the list Expected results: - messaging-app should be displayed with a new page showing the photo as an attachment, and nothing else Actual results: - messaging-app shows the restored state from when it was last run (the values entered in Step 3 above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1429899/+subscriptions -- Mailing list: https://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 1436538] Re: brigtness slider should not allow total darkness
Exactly what it says, which is perhaps not helpful :-) The cache partition is used for downloads, etc which are in your browser (and other) caches. It should contain only transient data. One notable data type stored here are OTA updates before they are installed. In your case, I don't imagine resetting it will change anything. On 16 April 2015 at 11:01, Joseph Wakeling j...@webdrake.net wrote: @John -- thanks very much for the feedback. One question: what does the wipe cache partition option mean (as opposed to the factory reset, which is obvious)? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427946] Re: unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() on exit
I suspect at shutdown, the QScreen backing the qquickwindow is deleted before the qquickwindow is closed - when that happens, qt still has gl resources it wants to release, so tries to acquire a new shared gl context and release them, before shutting down properly. But this causes qtmir to try creating a new QPlatformOpenGLContext which tries to create a Display, while mir is shutting down, and I suspect the egl state is not suited to that. Proper solution is to implement a QPlatformOffscreenSurface and use it on shutdown ** Changed in: mir (Ubuntu) Status: New = Invalid ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir (Ubuntu) Status: New = Confirmed ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Status: New = Triaged ** Changed in: qtmir Importance: Undecided = High ** Changed in: qtmir Assignee: (unassigned) = Gerry Boland (gerboland) -- 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/1427946 Title: unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() on exit Status in Qt integration with the Mir display server: Triaged Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Triaged Bug description: Unity8 aborts on exit with: terminate called after throwing an instance of 'boost::exception_detail::clone_implboost::exception_detail::error_info_injectorstd::runtime_error ' what(): Nested Mir Display Error: Failed to update EGL surface. https://errors.ubuntu.com/problem/fc69b4f16d4d4571c83038bf9dc47b84135d9ced ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150302-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Wed Mar 4 02:22:30 2015 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2014-12-10 (83 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141209) ProcCmdline: unity8 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity8 StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/i386-linux-gnu/libmirserver.so.30 Title: unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1427946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429899] Re: StateSaver should not restore when app launched from content-hub
** Branch unlinked: lp:~zsombi/ubuntu-ui-toolkit/disable-statesaver- from-urihandler -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1429899 Title: StateSaver should not restore when app launched from content-hub Status in content-hub package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Testing the messaging-app state saving ability that we've been adding from this MR: https://code.launchpad.net/~tiagosh/messaging-app/state-saver2/+merge/250996 deb can be found here: http://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-vivid-armhf/1669/artifact/work/output/*zip*/output.zip The problem is, when the app is launched from the content-hub, the StateSaver still tries to restore it's previously saved state, but it should not and this causes problems. It should clear the state, the same way it does when launched via url-dispatcher. According to Ken, there are content-hub signals that StateSaver will need to listen to in order to know when the app is being launched by content-hub. To reproucde: 1) install the messaging-app deb from above 2) open messaging-app, swipe from bottom to create a new message 3) type some names in the recipient field, and type some message in the send field 4) do kill -2 pidOfMessagingApp to kill the messaging-app and save it's state 5) open camera-app and go to the photo roll 6) press Share from toolbar and select messaging-app from the list Expected results: - messaging-app should be displayed with a new page showing the photo as an attachment, and nothing else Actual results: - messaging-app shows the restored state from when it was last run (the values entered in Step 3 above) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1429899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444949] Re: Launcher reordering interrupted by second touch causes launcher confusion
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1444949 Title: Launcher reordering interrupted by second touch causes launcher confusion Status in the base for Ubuntu mobile products: New Status in unity8 package in Ubuntu: In Progress Bug description: Steps: * long-press on a launcher icon * drag the icon off the launcher * tap somewhere with a second finger Expected: * drag is cancelled Current: * launcher goes away but remains in drag state ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150409.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.1-0ubuntu2 Architecture: armhf Date: Thu Apr 16 10:11:35 2015 InstallationDate: Installed on 2015-04-16 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150416-020203) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
Hi, guys. I am also actively testing to reproduce similar issue (that our customer complained about) - I'm deploying three unit percona-cluster (each unit in a separate LXC on separate physical machine) with three unit keystone (both services have hacluster subodinated), but failed to reproduce it so far - we made sure everything is set up correctly, run 'keystone service-list' and similar, did a hard-reset via IPMI of the node where percona-cluster VIP resides, corosync/pacemaker did their job, VIP moved, 'keystone service-list' is happy... I'll update here with more info as I go along. -- 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/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc Status in lxc package in Ubuntu: New Status in pacemaker package in Ubuntu: Confirmed Bug description: We've seen this a few times with three node clusters, all running in LXC containers; pacemaker fails to restart correctly as it can't communicate with corosync, resulting in a down cluster. Rebooting the containers resolves the issue, so suspect some sort of bad state either in corosync or pacemaker. Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: mcp_read_config: Configured corosync to accept connections from group 115: Library error (2) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: main: Starting Pacemaker 1.1.10 (Build: 42f2063): generated-manpages agent-manpages ncurses libqb-logging libqb-ipc lha-fencing upstart nagios heartbeat corosync-native snmp libesmtp Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: cluster_connect_quorum: Quorum acquired Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1000 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1003 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: get_node_name: Defaulting to uname -n for the local corosync node name Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: crm_update_peer_state: pcmk_quorum_notification: Node juju-machine-4-lxc-4[1001] - state is now member (was (null)) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: corosync_node_name: Unable to get node name for nodeid 1003 Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: crm_update_peer_state: pcmk_quorum_notification: Node (null)[1003] - state is now member (was (null)) Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: main: CRM Git Version: 42f2063 Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: corosync_node_name: Unable to get node name for nodeid 1001 Apr 2 11:41:32 juju-machine-4-lxc-4 stonith-ng[1033744]: notice: get_node_name: Defaulting to uname -n for the local corosync node name Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync Apr 2 11:41:32 juju-machine-4-lxc-4 corosync[1033732]: [MAIN ] Denied connection attempt from 109:115 Apr 2 11:41:32 juju-machine-4-lxc-4 corosync[1033732]: [QB] Invalid IPC credentials (1033732-1033746). Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: cluster_connect_cpg: Could not connect to the Cluster Process Group API: 11 Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: main: HA Signon failed Apr 2 11:41:32 juju-machine-4-lxc-4 attrd[1033746]:error: main: Aborting startup Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]:error: pcmk_child_exit: Child process attrd (1033746) exited: Network is down (100) Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: warning: pcmk_child_exit: Pacemaker child process attrd no longer wishes to be respawned. Shutting ourselves down. Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: pcmk_shutdown_worker: Shuting down Pacemaker Apr 2 11:41:32 juju-machine-4-lxc-4 pacemakerd[1033741]: notice: stop_child: Stopping crmd: Sent -15 to process 1033748 Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: warning: do_cib_control: Couldn't complete CIB registration 1 times... pause and retry Apr 2 11:41:32 juju-machine-4-lxc-4 crmd[1033748]: notice: crm_shutdown: Requesting shutdown, upper limit is 120ms Apr 2
[Touch-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness
@John thanks again for clarification. In any case I did a factory reset via the power+VolUp buttons. All back and working now. Perhaps a worthwhile feature request for the future, to have a reset option that resets device settings, without wiping data? :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1436538 Title: brigtness slider should not allow total darkness Status in the base for Ubuntu mobile products: Fix Released Status in indicator-power package in Ubuntu: Invalid Bug description: bq aquaris 4.5, Utopic Unicorn 20150312-002053: slider allows to minimize the brightess to the point of not seeing at all. Even if you manage to reboot (you don't see the confirmation dialogue) you still have completly dark display which effectively bricks the phone (no battery removal) unless you are patient enought to blindly try and hit long time enough to increase the brigtness again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1066157] Re: dash +orca does not speak the names of application icons
** Changed in: unity/7.2 Status: In Progress = Fix Committed ** Changed in: unity Assignee: (unassigned) = Luke Yelavich (themuso) ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Luke Yelavich (themuso) ** Changed in: unity (Ubuntu Trusty) Importance: Undecided = High -- 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/1066157 Title: dash +orca does not speak the names of application icons Status in OEM Priority Project: New Status in Unity: Fix Released Status in Unity 5.0 series: New Status in Unity 6.0 series: Won't Fix Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] Screen reader support for dynamic content in the Dash is enabled. [Test Case] (1) Enable Screen Reader (System Settings Universal Access Screen Reader) (2) Press Super + A to bring up the Applications lens of the Dash (3) Navigate displayed content (4) Choose an application for preview (5) Press Esc until the Dash is closed, repeat steps 2 to 4 You should hear the application description and preview description. [Regression Potential] Some new code deals with processing pointers: the usual problem potential of dealing with pointers in C code applies. [Other Info] This patch for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in public use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1066157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413773] Re: [Regressions] Dash dnd icons rendered behind dash.
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1413773 Title: [Regressions] Dash dnd icons rendered behind dash. Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [IMPACT] Dragged icons are rendered behind dash. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413411] Re: underscore in mounted drive name mishandled in menu
** Changed in: unity/7.2 Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1413411 Title: underscore in mounted drive name mishandled in menu Status in One Hundred Papercuts: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: Fix Committed Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] If you have a mounted drive with an underscore in it's name (e.g. host_S), then, when you right-click on the drive icon in the sidebar, the menu interprets the underscore as a keyboard-shortcut indicator, so shows the name as hostS (with S underlined). Hovering over the drive results in the correct host_S name; the bug is only in the right-click menu. Note that right-clicking on the Files icon will show a menu that includes the correct mounted disk names. It is only right-clicking on the drive-icons themselves that shows the incorrect name. [Test Case] (1) Create a mountable device with an underscore in its volume name (eg. host_S). (2) Right click on the icon for tha drive in the Launcher. It should display the underscore character correctly as a part of the drive name, and not as an underline. [Regression Potential] None. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu Vivid Vervet dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1413411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798445] Re: can't discern between two files or folder with identical names
Thanks for the answer, I understand. -- 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/798445 Title: can't discern between two files or folder with identical names Status in Ayatana Design: New Status in Unity: Incomplete Status in Unity Files Lens: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Binary package hint: dash 1. create two folders/files with the same name (in two different locations). 2. press the BFB (Big Freakin Button aka Home Button) and search for that folder/file name see that there is no way to tell which folder/file is which. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: dash 0.5.5.1-7.2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Jun 16 17:50:38 2011 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dash UpgradeStatus: Upgraded to natty on 2011-04-21 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/798445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 953875] Re: Encrypted swap no longer mounted at bootup
Launchpad has imported 5 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=87717. 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-12-25T20:58:35+00:00 Vecu-bosseur wrote: Dear Developpers, My /etc/crypttab contains: cryptswap1 UUID=c836dd13-1b4e-4bfb-9be5-6e5d972aa75a /dev/urandom swap,offset=2048,cipher=aes-cbc-essiv:sha256 And my /etc/fstab contains: /dev/mapper/cryptswap1 none swap sw 0 0 And this worked fine with cryptdisks_start however the option offset is not understood by systemd 215. I did change init system from sysvinit to systemd, and now, after 2 reboots, I don't have any swap and my device that had UUID c836dd13-1b4e-4bfb-9be5-6e5d972aa75a has seen its start erased, and thus its UUID itself, as if I had not mentioned an offset=0 in crypttab. The use case for offset=2048 is to be able to use a UUID to identify the partition I want to have encrypted swap on. Not using an offset=0 parameter would unconditionally erase the whole partition, including the portion where its UUID is stored. Using any other way to identify a partition can thus cause data loss if I reparttion my disk and forget to update /etc/crypttab. Please make systemd understand the offset= paramater of /etc/crypttab. Has this problem been addressed in a subsequent systemd version? Note: related to debian bug #751707 ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751707 ) Thanks, Vecu Bosseur Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/29 On 2014-12-26T01:37:53+00:00 zbyszek wrote: It's a long-standing well-known limitation: /* Options Debian's crypttab knows we don't: offset= skip= precheck= check= checkargs= noearly= loud= keyscript= */ Some of those will probably never be implemented (noearly, keyscript, loud, ...), but offset certainly should. Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/30 On 2015-04-16T11:53:47+00:00 Martin Pitt wrote: Created attachment 115118 cryptsetup: Implement offset and skip options Simple patch. Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/74 On 2015-04-16T11:54:21+00:00 Martin Pitt wrote: Created attachment 115119 reproducer/test script This is the reproducer and test script which I used. Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/75 On 2015-04-16T11:57:12+00:00 zbyszek wrote: I think a failure to parse those parameters should be fatal. It's just to dangerous to continue. Also meatadata in description :) Reply at: https://bugs.launchpad.net/ubuntu/+source/ecryptfs- utils/+bug/953875/comments/76 ** Changed in: systemd Status: Unknown = Confirmed ** Changed in: systemd Importance: Unknown = Medium -- 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/953875 Title: Encrypted swap no longer mounted at bootup Status in eCryptfs: Fix Released Status in systemd: Confirmed Status in ecryptfs-utils package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in ubiquity package in Ubuntu: Fix Released Status in ecryptfs-utils source package in Vivid: Fix Released Status in systemd source package in Vivid: Fix Committed Status in ubiquity source package in Vivid: Fix Released Status in systemd package in Debian: Confirmed Bug description: SUMMARY === During installation with encrypt my home folder mode, a broken /etc/crypttab gets created which defines a non-existing swap device (usually cryptswap1) with a UUID. This will also be put into /etc/fstab. As after installation the UUID does not exist, such systems don't have any actual swap. UPGRADE FIX === An upgrade to Ubuntu 15.04 (vivid) will detect and comment out these broken swap devices from /etc/fstab and /etc/crypttab. If you actually want to use those, do these steps: - Find the swap device that was meant to be used in sudo fdisk -l (it should say Linux swap in the last column), remember the device name (something like /dev/sda5) - Find the UUID in /etc/crypttab (the long alphanumeric ID after UUID=) - Run sudo mkswap -U 1234... /dev/sda5, replacing 1234 with the above UUID, and /dev/sda5 with the device name from step 1.
[Touch-packages] [Bug 798445] Re: can't discern between two files or folder with identical names
The status change indicates this bug requires input from the Ayatana design team before and more progress can be made in the Unity desktop shell software. -- 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/798445 Title: can't discern between two files or folder with identical names Status in Ayatana Design: New Status in Unity: Incomplete Status in Unity Files Lens: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Binary package hint: dash 1. create two folders/files with the same name (in two different locations). 2. press the BFB (Big Freakin Button aka Home Button) and search for that folder/file name see that there is no way to tell which folder/file is which. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: dash 0.5.5.1-7.2ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Jun 16 17:50:38 2011 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dash UpgradeStatus: Upgraded to natty on 2011-04-21 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/798445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427946] Re: unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() on exit
** Changed in: unity8 (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1427946 Title: unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() on exit Status in Qt integration with the Mir display server: Triaged Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: Unity8 aborts on exit with: terminate called after throwing an instance of 'boost::exception_detail::clone_implboost::exception_detail::error_info_injectorstd::runtime_error ' what(): Nested Mir Display Error: Failed to update EGL surface. https://errors.ubuntu.com/problem/fc69b4f16d4d4571c83038bf9dc47b84135d9ced ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150302-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 Date: Wed Mar 4 02:22:30 2015 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2014-12-10 (83 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha i386 (20141209) ProcCmdline: unity8 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity8 StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/i386-linux-gnu/libmirserver.so.30 Title: unity8 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1427946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444937] Re: QML cache gets stale too easily
(my guess / vague memory is that app upgrades are also already handled similar to image upgrades, but it's better to check) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1444937 Title: QML cache gets stale too easily Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: It's happened many times now that after looking for an issue the source of it ended up to be stale QML cache. We need the cache to be cleared more aggressively, likely on any QML- related package installation. App-specific cache should be (if it's not) cleared on install (or maybe better - removal) and upgrade. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libqt5qml5 5.4.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 12:25:21 2015 SourcePackage: qtdeclarative-opensource-src SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1444937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444949] [NEW] Launcher reordering interrupted by second touch causes launcher confusion
Public bug reported: Steps: * long-press on a launcher icon * drag the icon off the launcher * tap somewhere with a second finger Expected: * drag is cancelled Current: * launcher goes away but remains in drag state ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150409.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.1-0ubuntu2 Architecture: armhf Date: Thu Apr 16 10:11:35 2015 InstallationDate: Installed on 2015-04-16 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150416-020203) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Medium Assignee: Michael Zanetti (mzanetti) Status: In Progress ** Tags: apport-bug armhf vivid ** Branch linked: lp:~mzanetti/unity8/fix-dnd-cancelling ** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1444949 Title: Launcher reordering interrupted by second touch causes launcher confusion Status in unity8 package in Ubuntu: In Progress Bug description: Steps: * long-press on a launcher icon * drag the icon off the launcher * tap somewhere with a second finger Expected: * drag is cancelled Current: * launcher goes away but remains in drag state ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150409.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.1-0ubuntu2 Architecture: armhf Date: Thu Apr 16 10:11:35 2015 InstallationDate: Installed on 2015-04-16 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150416-020203) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1444949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443413] Re: can't boot with systemd
Ah, so not quite bug 953875, but a custom LVM setup. Adding /dev/dm-6 to crypttab does sound dangerous, as these are not very stable. Adding /dev/mapper/vg-swap or UUID=fdd.. to crypttab is usually better. What does ls -l /dev/mapper/vg-swap say, does it actually point to dm-6? If not, that's the problem, can you try with the stable symlinks? If it does point to dm-6, can you please boot with the debug shell as per /usr/share/doc/systemd/README.Debian, and when it hangs capture journalctl -b /home/you/journal.txt and then reboot and attach journal.txt here? Thanks! -- 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/1443413 Title: can't boot with systemd Status in systemd package in Ubuntu: Incomplete Bug description: Booting with systemd fails always at same stage. Using upstart just works. grep GRUB_CMDLINE_LINUX /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT= GRUB_CMDLINE_LINUX=systemd.log_target=kmsg systemd.log_level=debug grep debug /boot/grub/grub.cfg linux /vmlinuz-3.19.0-13-generic root=/dev/mapper/vg-root ro systemd.log_target=kmsg systemd.log_level=debug Sadly systemd-debug doesn't reveals more information what fails :-( lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1443413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443413] Re: can't boot with systemd
Sorry, my previous reply was quite bogus, too early still. I suppose that output comes from under upstart, so /dev/mapper/vg-swap is the *result* of crypttab. The blurred screenshot says invalid argument. So please leave that line disabled, and once the system is running, try sudo SYSTEMD_LOG_LEVEL=debug strace -fvvs1024 -o /tmp/t /lib/systemd /systemd-cryptsetup attach vg-swap dev/dm-6 /dev/urandom swap,cipher =aes-cbc-essiv:sha256 This should give some invalid argument at some point, does it? For me this command works fine on current vivid. If it reproduces the invalid argument for you, please copypaste the output and /tmp/t. Thanks! ** Summary changed: - can't boot with systemd + boot fails on cryptsetup random swap partition with invalid argument -- 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/1443413 Title: boot fails on cryptsetup random swap partition with invalid argument Status in systemd package in Ubuntu: Incomplete Bug description: Booting with systemd fails always at same stage. Using upstart just works. grep GRUB_CMDLINE_LINUX /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT= GRUB_CMDLINE_LINUX=systemd.log_target=kmsg systemd.log_level=debug grep debug /boot/grub/grub.cfg linux /vmlinuz-3.19.0-13-generic root=/dev/mapper/vg-root ro systemd.log_target=kmsg systemd.log_level=debug Sadly systemd-debug doesn't reveals more information what fails :-( lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1443413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431566] Re: Close/minimize/maximize buttons remain when switching from windowed to phone mode
** Branch linked: lp:~feng-kylin/unity8/fix-lp1431566 -- 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/1431566 Title: Close/minimize/maximize buttons remain when switching from windowed to phone mode Status in unity8 package in Ubuntu: Triaged Bug description: How to reproduce: 1) Switch to windowed mode. 2) Maximize an application (it does not matter which one, even the dash is ok). 3) Switch back to phone mode. 4) Bring the application which you previously maximed to the foreground. What happens: The close/minimize/maximize buttons are still there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1431566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444937] [NEW] QML cache gets stale too easily
Public bug reported: It's happened many times now that after looking for an issue the source of it ended up to be stale QML cache. We need the cache to be cleared more aggressively, likely on any QML- related package installation. App-specific cache should be (if it's not) cleared on install (or maybe better - removal) and upgrade. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libqt5qml5 5.4.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 12:25:21 2015 SourcePackage: qtdeclarative-opensource-src SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1444937 Title: QML cache gets stale too easily Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: It's happened many times now that after looking for an issue the source of it ended up to be stale QML cache. We need the cache to be cleared more aggressively, likely on any QML- related package installation. App-specific cache should be (if it's not) cleared on install (or maybe better - removal) and upgrade. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libqt5qml5 5.4.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 12:25:21 2015 SourcePackage: qtdeclarative-opensource-src SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1444937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436074] Re: tab previews black [arale only]
Built in landing-002. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1436074 Title: tab previews black [arale only] Status in the base for Ubuntu mobile products: Confirmed Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: running vivid-proposed build 146 on arale When I swipe from bottom edge to reveal tabs, only the most recent tab has a preview. The other tabs are black where the preview should be. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444975] [NEW] [UbuntuShape] Rendering issue with VMware's Gallium 0.4 on SVGA3D
Public bug reported: The resolution independent rendering of the UbuntuShape is wrong on VMware's Gallium on SVGA3D renderer. This is due to a bad handling of dFd*() functions in branches. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Critical Assignee: Loïc Molinari (loic.molinari) Status: In Progress ** Branch linked: lp:~loic.molinari/ubuntu-ui-toolkit/ubuntu-ui-toolkit- vmware-gallium-rendering-fix -- 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/1444975 Title: [UbuntuShape] Rendering issue with VMware's Gallium 0.4 on SVGA3D Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: The resolution independent rendering of the UbuntuShape is wrong on VMware's Gallium on SVGA3D renderer. This is due to a bad handling of dFd*() functions in branches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1444975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312976] Re: Make NFS client/server work under systemd
** Bug watch added: Debian Bug tracker #782700 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782700 ** Also affects: apparmor (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782700 Importance: Unknown Status: Unknown -- 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/1312976 Title: Make NFS client/server work under systemd Status in apparmor package in Ubuntu: Fix Released Status in nfs-utils package in Ubuntu: Fix Released Status in rpcbind package in Ubuntu: Fix Released Status in apparmor package in Debian: Unknown Status in rpcbind package in Debian: New Bug description: nfs-utils can not be used with systemd due to missing systemd unit or init.d script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1312976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438662] Re: Calendar sync is not happening
Ok, Thanks renatofilho -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1438662 Title: Calendar sync is not happening Status in the base for Ubuntu mobile products: In Progress Status in Sync monitor for Ubuntu Touch: Invalid Status in syncevolution package in Ubuntu: In Progress Status in syncevolution package in Ubuntu RTM: In Progress Bug description: STEPS: 1. Install calendar 2. Step up your google account 3. Enable accounts to use calendar 4. Tap on the sync option in Calendar EXPECTED: I expect it to update my calendar and notifications ACTUAL: In .cache/upstart/sync-monitor.log I see lots of error : error code from SyncEvolution remote, status 400: updateAllSubItems REPORT 'list items': bad HTTP status: status 1.1, code 400, class 4, Bad Request and error : error code from SyncEvolution remote, status 400: REPORT 'meta data': bad HTTP status: status 1.1, code 400, class 4, Bad Request and sync doesn't happen We are assuming this is a change on googles side that affects us on both vivid and rtm. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1438662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444995] [NEW] It's impossible back to a window if there is another window with always on top enable
Public bug reported: - Open 2 or more windows of the same program, as expected, they will be agrouped in the same icon in panel - With one of that, put in a non-maximized small size window, righ click on its title bar, and enable Always on top - open a windows of another program and maximize it. As expected, you can open and navigate to any other programs besides the window on top in a part of screen. But the problem is: You can't come back to the first program windows, except for that is with Always on top enabled. Is expected that the user can choose any open window to open (back the always on top window). But it's impossible, you need to minimize all other windows to back to the other windows opened of that application. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Apr 16 09:46:57 2015 InstallationDate: Installed on 2015-03-30 (16 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1444995 Title: It's impossible back to a window if there is another window with always on top enable Status in unity package in Ubuntu: New Bug description: - Open 2 or more windows of the same program, as expected, they will be agrouped in the same icon in panel - With one of that, put in a non-maximized small size window, righ click on its title bar, and enable Always on top - open a windows of another program and maximize it. As expected, you can open and navigate to any other programs besides the window on top in a part of screen. But the problem is: You can't come back to the first program windows, except for that is with Always on top enabled. Is expected that the user can choose any open window to open (back the always on top window). But it's impossible, you need to minimize all other windows to back to the other windows opened of that application. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-34.47~14.04.1-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Apr 16 09:46:57 2015 InstallationDate: Installed on 2015-03-30 (16 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.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/1444995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438662] Re: Calendar sync is not happening
ok, that's explain. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1438662 Title: Calendar sync is not happening Status in the base for Ubuntu mobile products: In Progress Status in Sync monitor for Ubuntu Touch: Invalid Status in syncevolution package in Ubuntu: In Progress Status in syncevolution package in Ubuntu RTM: In Progress Bug description: STEPS: 1. Install calendar 2. Step up your google account 3. Enable accounts to use calendar 4. Tap on the sync option in Calendar EXPECTED: I expect it to update my calendar and notifications ACTUAL: In .cache/upstart/sync-monitor.log I see lots of error : error code from SyncEvolution remote, status 400: updateAllSubItems REPORT 'list items': bad HTTP status: status 1.1, code 400, class 4, Bad Request and error : error code from SyncEvolution remote, status 400: REPORT 'meta data': bad HTTP status: status 1.1, code 400, class 4, Bad Request and sync doesn't happen We are assuming this is a change on googles side that affects us on both vivid and rtm. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1438662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
** Also affects: xserver Importance: Undecided Status: New ** No longer affects: xserver -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Linux-Kernel-Headers - Headers Files for the Linux Kernel: New Status in Mesa: New Status in Ubuntu UX bugs: New Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418077] Re: After connection drops, mobile-data takes ~5m to re-connect
** Changed in: canonical-devices-system-image Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1418077 Title: After connection drops, mobile-data takes ~5m to re-connect Status in the base for Ubuntu mobile products: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: If the mobile data connection drops due to signal loss or modem reset ( eg. changing radio technology, setting 3g slot, ... ), there's a delay of 5m before NetworkManager attempts to re-connect. The original bug pertained to changing the radio technology ( which causes the modem to unregister and then re-register using the new technology ), however the problem is more generic. The steps to reproduce focus on this case, as this is the easiest way to get the modem to drop the connection for long enough for the problem to occur. Forcing the modem to disconnect via wrapping the device in tin-foil should also trigger the problem. Steps to reproduce: 1. Confirm cellular data (disable wifi) 2. Change TechnologyPreference on online SIM 3. Confirm no cellular data 4. Wait ~10 minutes 5. Confirm cellular data What happens: Changing something on the modem causes cellular data to disappear for 10 minutes What should happen: It should behave as before, i.e. cellular data should come back immediately current build number: 97 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-02 12:48:25 version version: 97 version ubuntu: 20150202 version device: 20150128-5379bdb version custom: 20150202 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385619] Re: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev
Statically linking gtk+ is uncommon and discouraged by gtk+ developers (see Extra Configuration Options in [1]). Also, I don't think we should increase the package size for such an uncommon a use case. Please compile gtk+ yourself if you want to link your application to it statically. [1] https://developer.gnome.org/gtk3/stable/gtk-building.html ** Changed in: gtk+3.0 (Ubuntu) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1385619 Title: libgtk-3.a and libgdk-3.a missing in libgtk-3-dev Status in The Linux Mint Distribution: New Status in gtk+3.0 package in Ubuntu: Won't Fix Bug description: The static libraries are missing in libgtk-3-dev 3.10.8~6+qiana. Upstream (Ubuntu) also has this issue, but since this is a specialized qiana build, I felt I should also report this here. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1385619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1101157] Re: libgdk-pixbuf2.0-dev unusable for static builds
Statically linking gtk+ is uncommon and discouraged by gtk+ developers (see Extra Configuration Options in [1]). Also, I don't think we should increase the package size for such an uncommon a use case. Please compile gtk+ yourself if you want to link your application to it statically. [1] https://developer.gnome.org/gtk3/stable/gtk-building.html ** Changed in: gdk-pixbuf (Ubuntu) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1101157 Title: libgdk-pixbuf2.0-dev unusable for static builds Status in gdk-pixbuf package in Ubuntu: Won't Fix Bug description: The package does not provide a static version of library. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1101157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445016] [NEW] Having access to the page header component would be useful
Public bug reported: Using vivid, currently the pagestack/page try to be smart with the header and adjust margins as needed, but that doesn't always work and it would be nice to have access to the header component to be able to e.g anchor on header.bottom small testcase example attached, the intend is to center the label but it's not easy to do (you can do it by tweaking the topMargin though) (note that the code is inspired from the system settings updates panel and bug #1429280) ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Attachment added: small example showing the issue https://bugs.launchpad.net/bugs/1445016/+attachment/4377193/+files/center.qml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1445016 Title: Having access to the page header component would be useful Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Using vivid, currently the pagestack/page try to be smart with the header and adjust margins as needed, but that doesn't always work and it would be nice to have access to the header component to be able to e.g anchor on header.bottom small testcase example attached, the intend is to center the label but it's not easy to do (you can do it by tweaking the topMargin though) (note that the code is inspired from the system settings updates panel and bug #1429280) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1445016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443971] Re: Call waiting - wrong call hung up
** Branch linked: lp:ubuntu/vivid-proposed/dialer-app -- 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/1443971 Title: Call waiting - wrong call hung up Status in the base for Ubuntu mobile products: New Status in Dialer app for Ubuntu Touch: In Progress Status in dialer-app package in Ubuntu: In Progress Status in dialer-app package in Ubuntu RTM: New Bug description: Version: ubuntu-touch/rc/bq-aquaris.en r22 krillin Steps to reproduce: * Ensure call waiting enabled on DUT * Call the DUT from phone X * Accept the call, verify established * Call the DUT from phone Y * Accept the call, verify new call to Y established, phone X on hold * Hit Switch Call button * Verify back to talking to phone X * Hit the hang up button Expected result: - Call with Phone X ended - Call with Phone Y maintained Actual result: - Call with Phone Y ended - Call with Phone X maintained To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443971/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.
@pat, what is the behaviour we should see, since it seems not to be the exactly requested behaviour in the bug description. -- 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/1367818 Title: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state. Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Bug description: - When the sound is muted, the volume icon to the left of the volume slider should have a red / running through it. - Add an explicit Mute button to the sound indicator menu. - Pressing and holding the icon to the left of the volume slider should mute volume straight away. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441210] Re: Roboto fonts make printer crash (fonts-android)
@Jean-Sebastien: Any chance that you can test fonts-roboto in my PPA? I'm disinclined to propose a change to 14.04 without knowing that it fixes the issue. ** Changed in: fonts-android (Ubuntu) Status: In Progress = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1441210 Title: Roboto fonts make printer crash (fonts-android) Status in fonts-android package in Ubuntu: Incomplete Status in fonts-android package in Debian: New Bug description: As per https://code.google.com/p/android/issues/detail?id=38383, there has been issues with the Roboto font family regarding printing. These issues seem to have been resolved in the new version of the fonts made available by Google in 2014 here http://developer.android.com/design/style/typography.html. My setup: 1) Release: Ubuntu 14.04 LTS 2) Package: fonts-roboto 1:4.3-3ubuntu1.1 3) Expected Results: When using Roboto fonts in a document (pdf, odf, etc.), I should be able to print the document. 4) Current Results: Roboto fonts make the printer crash instead of printing. The printer I am using is a HP-Laser Jet P2055. Steps to reproduce: Install fonts-roboto package from Ubuntu Software Center. Produce a document in Libre Office with Roboto font and send to printer. Printer is crashing, need hard reboot. Workaround: (1) Remove fonts-roboto package from Ubuntu Software Center. (2) Download new version of the fonts made available by Google and save them in the .fonts folder in home directory. (3) Produce a new document with Roboto font and send to printer. (4) Document is printing. Basically, I think this package just need to be updated to use the latest fonts issued by Google. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1441210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443971] Re: Call waiting - wrong call hung up
This bug was fixed in the package dialer-app - 0.1+15.04.20150415.2-0ubuntu1 --- dialer-app (0.1+15.04.20150415.2-0ubuntu1) vivid; urgency=medium [ Gustavo Pichorim Boiko ] * Make sure the correct call is finished when pressing the hangup button on a multi-call scenario. Also add autopilot tests to avoid this happening in the future. (LP: #1443971) -- CI Train Bot ci-train-...@canonical.com Wed, 15 Apr 2015 18:28:36 + ** Changed in: dialer-app (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1443971 Title: Call waiting - wrong call hung up Status in the base for Ubuntu mobile products: New Status in Dialer app for Ubuntu Touch: In Progress Status in dialer-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu RTM: New Bug description: Version: ubuntu-touch/rc/bq-aquaris.en r22 krillin Steps to reproduce: * Ensure call waiting enabled on DUT * Call the DUT from phone X * Accept the call, verify established * Call the DUT from phone Y * Accept the call, verify new call to Y established, phone X on hold * Hit Switch Call button * Verify back to talking to phone X * Hit the hang up button Expected result: - Call with Phone X ended - Call with Phone Y maintained Actual result: - Call with Phone Y ended - Call with Phone X maintained To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443971/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423185] Re: Calendar app crash
Do I understand this bug correctly? It seems to have tasks for the image (qtorganizer5-eds) which are fixed in the 'ww13-ota' milestone. It then seems to be marked 'in progress' for the app itself. I would conclude that this will still be broken on a test device running the OTA image and the calendar app in the store? FWIW, have such a handset, and this bug reproduced easily if I selected a day prior to 'today' in the year view. It did not seem to reproduce with future dates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1423185 Title: Calendar app crash Status in the base for Ubuntu mobile products: Fix Released Status in Calendar application for Ubuntu devices: In Progress Status in qtorganizer5-eds package in Ubuntu: Fix Released Status in qtorganizer5-eds package in Ubuntu RTM: Fix Released Bug description: Tapping on a day in Year view, crashed calendar app. See attached file. TEST CASE: 1. Switch to 'Year' view 2. Tap on any day 3. Repeat steps 1 and 2 up to 10 times ACTUAL RESULT The app crashes after a few attempts To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1423185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408721] Re: package libgtk-3-0 3.14.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of pack
This is very strange... did you ever rebuild a gtk+3.0 package yourself, or install from a PPA? ** Changed in: gtk+3.0 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1408721 Title: package libgtk-3-0 3.14.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:i386 Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Rolling release failure after an upgrade. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libgtk-3-0 3.14.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 Date: Thu Jan 8 19:59:38 2015 DuplicateSignature: package:libgtk-3-0:3.14.6-0ubuntu1:trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:i386 ErrorMessage: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:i386 InstallationDate: Installed on 2014-12-16 (23 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20141214) SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.14.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/gtk-3.0/settings.ini', which is different from other instances of package libgtk-3-0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1408721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443413] Re: boot fails on cryptsetup random swap partition with invalid argument
** Attachment added: strace of /lib/systemd/systemd-cryptsetup attach vg-swap /dev/dm-6 /dev/urandom swap,cipher=aes-cbc-essiv:sha256 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1443413/+attachment/4377259/+files/tt -- 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/1443413 Title: boot fails on cryptsetup random swap partition with invalid argument Status in systemd package in Ubuntu: Incomplete Bug description: Booting with systemd fails always at same stage. Using upstart just works. grep GRUB_CMDLINE_LINUX /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT= GRUB_CMDLINE_LINUX=systemd.log_target=kmsg systemd.log_level=debug grep debug /boot/grub/grub.cfg linux /vmlinuz-3.19.0-13-generic root=/dev/mapper/vg-root ro systemd.log_target=kmsg systemd.log_level=debug Sadly systemd-debug doesn't reveals more information what fails :-( lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1443413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445035] [NEW] Poor quality of photos - consider the use of software jpeg
Public bug reported: Image quality on the bq aquaris phone is relatively low even on the highest quality setting. Numerous compression artifacts are visible like on pictures taken with a cheap Chinese tablet. On the other hand, imagemagick convert takes 2s on this CPU when converting 8 MP bmp file to jpeg. So please consider using software jpeg for the highest quality setting. ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Tags: quality -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1445035 Title: Poor quality of photos - consider the use of software jpeg Status in camera-app package in Ubuntu: New Bug description: Image quality on the bq aquaris phone is relatively low even on the highest quality setting. Numerous compression artifacts are visible like on pictures taken with a cheap Chinese tablet. On the other hand, imagemagick convert takes 2s on this CPU when converting 8 MP bmp file to jpeg. So please consider using software jpeg for the highest quality setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1445035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
I get this, too, with a .crash file from qemu that for some reason seems to be truncated after the USerGroups section !? Attaching the .crash file causing this issue. [apport-bug also has issues with this file.] ** Attachment added: _usr_bin_qemu-system-x86_64.117.crash https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+attachment/4377294/+files/_usr_bin_qemu-system-x86_64.117.crash -- 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/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Confirmed Bug description: When running apport-unpack to get at a core dump laney@raleigh sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File /usr/bin/apport-unpack, line 73, in module pr.extract_keys(f, bin_keys, dir) File /usr/lib/python3/dist-packages/problem_report.py, line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1088957] Re: [ThinkPad T420] hda-intel: spurious response - audio dropping out during playback
[4.530969] current rate 47872 is different from the runtime rate 48000 [4.532567] current rate 47872 is different from the runtime rate 48000 [4.542074] current rate 47872 is different from the runtime rate 48000 [4.543663] current rate 47872 is different from the runtime rate 48000 [6.988084] alx :03:00.0 eth0: NIC Up: 1 Gbps Full [7.556984] alx :03:00.0 eth0: Link Down [9.742737] alx :03:00.0 eth0: NIC Up: 1 Gbps Full [ 12.853590] current rate 47872 is different from the runtime rate 48000 [ 12.855306] current rate 47872 is different from the runtime rate 48000 [ 12.865532] current rate 47872 is different from the runtime rate 48000 [ 12.867129] current rate 47872 is different from the runtime rate 48000 [ 21.292335] current rate 47872 is different from the runtime rate 48000 [ 21.293919] current rate 47872 is different from the runtime rate 48000 [ 31.830409] audit_printk_skb: 108 callbacks suppressed [ 31.830411] type=1400 audit(1429190327.831:47): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2503 comm=apparmor_parser [ 31.830414] type=1400 audit(1429190327.831:48): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2503 comm=apparmor_parser [ 31.830678] type=1400 audit(1429190327.831:49): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2503 comm=apparmor_parser [ 598.180586] current rate 47872 is different from the runtime rate 48000 [ 598.182285] current rate 47872 is different from the runtime rate 48000 [ 1192.928332] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. [ 1422.073507] hda-intel :00:1b.0: Unstable LPIB (32768 = 2048); disabling LPIB delay counting [ 5273.853061] current rate 47872 is different from the runtime rate 48000 [ 5273.854661] current rate 47872 is different from the runtime rate 48000 [ 5289.156834] current rate 47872 is different from the runtime rate 48000 [ 5289.158392] current rate 47872 is different from the runtime rate 48000 -- 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/1088957 Title: [ThinkPad T420] hda-intel: spurious response - audio dropping out during playback Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am testing on raring. To reproduce try playing a you tube video, the audio will go in and out. In addition playing back music in rhythmbox will also exhibit the same problems. When looking at dmesg I see the following lines: [ 1653.495497] hda-intel: spurious response 0x40:0x3, last cmd=0x30270503 [ 1653.495498] hda-intel: spurious response 0x4011:0x3, last cmd=0x30270503 [ 1653.495500] hda-intel: spurious response 0x0:0x3, last cmd=0x30270503 [ 1653.495501] hda-intel: spurious response 0x5:0x3, last cmd=0x30270503 [ 1654.591127] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x301f0500 Eventually after this the audio cuts out complete and nothing can be heard. Not sure if this is a pulseaudio bug or an intel driver bug. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8 Uname: Linux 3.7.0-5-generic x86_64 ApportVersion: 2.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arges 2340 F pulseaudio /dev/snd/pcmC0D0p: arges 2340 F...m pulseaudio Date: Tue Dec 11 09:20:33 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2012-08-17 (116 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120807.2) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to raring on 2012-11-26 (14 days ago) dmi.bios.date: 11/28/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET67WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET67WW(1.37):bd11/28/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4177CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1088957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
nazgul@rivendell:~$ dpkg -la apport Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten | Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/ Halb installiert/Trigger erWartet/Trigger anhängig |/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht) ||/ Name Version Architektur Beschreibung +++-=-=-=- ii apport2.17.1-0ubuntu2 all automatically generate crash reports for debugging -- 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/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Confirmed Bug description: When running apport-unpack to get at a core dump laney@raleigh sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File /usr/bin/apport-unpack, line 73, in module pr.extract_keys(f, bin_keys, dir) File /usr/lib/python3/dist-packages/problem_report.py, line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444626] Re: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav
** Branch linked: lp:~townsend/unity/fix-quicklist-keynav-left -- 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/1444626 Title: When in Quicklist keynav, using left arrow to exit Quicklist should enter Launcher keynav Status in Unity: In Progress Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: In Progress Bug description: When using the arrow keys to navigate a Quicklist and using the left arrow key to exit the Quicklist, Launcher keynav should activate and on the icon for which the Quicklist was active. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1444626/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1441975] Re: have not shadows
*** This bug is a duplicate of bug 1417615 *** https://bugs.launchpad.net/bugs/1417615 ** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-mate-artwork -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1441975 Title: have not shadows Status in One Hundred Papercuts: Triaged Status in Themes for Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: nautilus and desktop have not shadows on context menus ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 9 08:54:22 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2015-03-05 (34 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150305) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2015-03-05T22:46:49.143864 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1441975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445064] [NEW] Re-implement container crash forwarding
Public bug reported: The container crash forwarding feature must be re-implemented to use a safe design. The current thought is: - Introduce a systemd unit and upstart job to have a socket activated apport crash handler - When a crash comes from a container, have apport connect to the socket in the crashed process' root, write the arguments it received to the socket. - The crash handler in the container will then run and close the socket when it doesn't need the crashed process anymore. - The host crash handler then exits. This means that we only rely on an accessible root directory for the crashed process and the crash handler will be spawned by init inside that container. This makes it safe for privileged and unprivileged containers. As an extra security measure, rate limiting should be added so that we can only have 10 in-flight crashes and that any crash taking more than 30s to be handled get cancelled (preventing host DoS). ** Affects: apport (Ubuntu) Importance: Wishlist Assignee: Stéphane Graber (stgraber) Status: Triaged -- 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/1445064 Title: Re-implement container crash forwarding Status in apport package in Ubuntu: Triaged Bug description: The container crash forwarding feature must be re-implemented to use a safe design. The current thought is: - Introduce a systemd unit and upstart job to have a socket activated apport crash handler - When a crash comes from a container, have apport connect to the socket in the crashed process' root, write the arguments it received to the socket. - The crash handler in the container will then run and close the socket when it doesn't need the crashed process anymore. - The host crash handler then exits. This means that we only rely on an accessible root directory for the crashed process and the crash handler will be spawned by init inside that container. This makes it safe for privileged and unprivileged containers. As an extra security measure, rate limiting should be added so that we can only have 10 in-flight crashes and that any crash taking more than 30s to be handled get cancelled (preventing host DoS). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1445064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
