[Touch-packages] [Bug 1346687] [NEW] Ubuntu 14 KVM Guest I/O Elevator Non-configurable
You have been subscribed to a public bug: Ubuntu 14.04 guest runs pretty much standard standard configuration: KVM hypervisor, ACPI and APIC enabled, virtio disk bus, raw storage format... While running this project, I am also involved in testing SSD drives across different Linux distributions and their support for discard option (TRIM). To cut the story short, Ubuntu-based KVM guest did not set any scheduler on the boot disk vda): # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk 1 0B 0B vda1 part 1 0B 0B vda2 part 1 0B 0B vda5 part 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B That is in stark contrast with other distributions running almost identical KVM guest configuration (with the exception of the root file system using BTRFS instead of EXT4 on SUSE). Oracle Linux 6.5: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk deadline 1 0B 0B vda1 part deadline 1 0B 0B vda2 part deadline 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B OpenSUSE 13.1: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom cfq 1 0B 0B vda disk cfq 1 0B 0B vda1 part cfq 1 0B 0B vda2 part cfq 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B Indeed, checking elevator capabilities for boot disk on Ubuntu KVM guest showed: # cat /sys/block/vda/queue/scheduler none Other Linux distributions show more options: # cat /sys/block/vda/queue/scheduler noop deadline [cfq] As well, attempts to change the elevator on Ubuntu guest fail. For example: # echo noop /sys/block/vda/queue/scheduler # echo $? 0 # cat /sys/block/vda/queue/scheduler none Setting it globally in /etc/default/grub and updating it via update- grub2 fails too. In the meantime, to automate check of elevators (schedulers) and discard support for SSD drives and thin-provisioned volumes on Linux, I wrote simple Perl script: http://www.circlingcycle.com.au/Unix-sources/Linux-check-IO-scheduler- and-discard-support.pl.txt Part of the results on RHEL 6.5 server would look like: INFO: I/O elevator (scheduler) and discard support summary INFO: Hard Disk sdb configured with I/O scheduler cfq INFO: SSD sda configured with I/O scheduler deadline supports discard operation INFO: Hard Disk sdc configured with I/O scheduler cfq INFO: Hard Disk sdi configured with I/O scheduler cfq INFO: Hard Disk sdh configured with I/O scheduler cfq The Ubuntu KVM guest runs latest paches: Linux ubuntu14-vm2.circlingcycle.com.au 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Regards, Dusan Baljevic VK2COT ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 14 KVM Guest I/O Elevator Non-configurable https://bugs.launchpad.net/bugs/1346687 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346687] Re: Ubuntu 14 KVM Guest I/O Elevator Non-configurable
As suggested, I added the package for /bin/lsblk. That is probably good enough for initial bug report. Dusan Baljevic ** Package changed: ubuntu = util-linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1346687 Title: Ubuntu 14 KVM Guest I/O Elevator Non-configurable Status in “util-linux” package in Ubuntu: New Bug description: Ubuntu 14.04 guest runs pretty much standard standard configuration: KVM hypervisor, ACPI and APIC enabled, virtio disk bus, raw storage format... While running this project, I am also involved in testing SSD drives across different Linux distributions and their support for discard option (TRIM). To cut the story short, Ubuntu-based KVM guest did not set any scheduler on the boot disk vda): # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk 1 0B 0B vda1 part 1 0B 0B vda2 part 1 0B 0B vda5 part 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B That is in stark contrast with other distributions running almost identical KVM guest configuration (with the exception of the root file system using BTRFS instead of EXT4 on SUSE). Oracle Linux 6.5: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk deadline 1 0B 0B vda1 part deadline 1 0B 0B vda2 part deadline 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B OpenSUSE 13.1: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom cfq 1 0B 0B vda disk cfq 1 0B 0B vda1 part cfq 1 0B 0B vda2 part cfq 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B Indeed, checking elevator capabilities for boot disk on Ubuntu KVM guest showed: # cat /sys/block/vda/queue/scheduler none Other Linux distributions show more options: # cat /sys/block/vda/queue/scheduler noop deadline [cfq] As well, attempts to change the elevator on Ubuntu guest fail. For example: # echo noop /sys/block/vda/queue/scheduler # echo $? 0 # cat /sys/block/vda/queue/scheduler none Setting it globally in /etc/default/grub and updating it via update- grub2 fails too. In the meantime, to automate check of elevators (schedulers) and discard support for SSD drives and thin-provisioned volumes on Linux, I wrote simple Perl script: http://www.circlingcycle.com.au/Unix-sources/Linux-check-IO-scheduler- and-discard-support.pl.txt Part of the results on RHEL 6.5 server would look like: INFO: I/O elevator (scheduler) and discard support summary INFO: Hard Disk sdb configured with I/O scheduler cfq INFO: SSD sda configured with I/O scheduler deadline supports discard operation INFO: Hard Disk sdc configured with I/O scheduler cfq INFO: Hard Disk sdi configured with I/O scheduler cfq INFO: Hard Disk sdh configured with I/O scheduler cfq The Ubuntu KVM guest runs latest paches: Linux ubuntu14-vm2.circlingcycle.com.au 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Regards, Dusan Baljevic VK2COT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1346687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305175] Re: openssl 1.0.1f 'ssl handshake failure' connection failure
Warning: Both RC4 and MD5 are INSECURE. They are susceptible to practical attacks. Do not use them. MD5 is already disabled by default. Real collisions have been produced, and used to forge certificates in the wild; its use as an HMAC is also strongly discouraged. It must never be used. RC4 (both RC4-MD5, RC4-SHA and other RC4 ciphers) is a very old stream cipher. It is thought some adversaries can already break it in real- time; in the public literature, several serious weaknesses have already been found (and at the time of writing, another one is on the way). An RFC will shortly be published - see https://tools.ietf.org/html/draft- popov-tls-prohibiting-rc4-02 - entirely prohibiting the use of all RC4 ciphersuites in all circumstances. Some browsers are already in the process of turning it off. Please see the results at: - https://www.ssllabs.com/ssltest/analyze.html?d=centinel1000.cardinalcommerce.com - https://www.ssllabs.com/ssltest/analyze.html?d=inaturalist.org which indicate that these sites have deep problems with their encryption. centinel1000.cardinalcommerce.com seems to be run from an outdated Windows Server 2003 using IIS/6.0 (which hits end-of-life in about a year). It only offers insecure ciphersuites RC4-MD5 RC4-SHA, and only over SSLv3 (it is intolerant of modern TLS 1.2 connections). You will see from the results that current versions of all mainstream browsers already refuse to connect to it, and in particular I must be clear it is NOT A BUG that curl and wget also refuse to do so - that is correct behaviour and should be regarded as bad as if it offered only 'export' ciphers. Its encryption is exploitably bad: I would consider it in breach of PCI requirements. inaturalist.com does not support TLS 1.2, uses RC4 (insecure) in preference to other ciphersuites, and offers 1024-bit DHE which is insecure. IE11 does the best it can there and connects with TLS_RSA_WITH_AES_128_CBC_SHA (0x2f); this is susceptible to BEAST, but not as bad as the above. The problem being reported by curl is that inaturalist.com is intolerant of TLS 1.2. This is also NOT A BUG with the client, but is a bug with the server. Some browsers retry with lower protocol versions automatically (and should use the downgrade SCSV to indicate this, as this is otherwise behaviour exploitable by an attacker); curl and wget do not. It is strongly likely that future versions of TLS libraries will completely ignore requests to use these ciphersuites: libReSSL disables it, and I think BoringSSL might too. At best, this is a stop-gap measure, but you should be aware the problem does not lie with you here. I suggest you contact the respective sites' security departments to inform them their encryption is weak. As this does not seem to be a bug in the client, I suggest closing this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1305175 Title: openssl 1.0.1f 'ssl handshake failure' connection failure Status in “openssl” package in Ubuntu: Confirmed Bug description: When attempting 'curl' or 'openssl s_client' I have been getting error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure openssl version OpenSSL 1.0.1f 6 Jan 2014 examples: ```Normal connect # openssl s_client -connect centinel1000.cardinalcommerce.com:443 -showcerts CONNECTED(0003) 140148901013152:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:s23_lib.c:177: --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0 bytes and written 317 bytes --- New, (NONE), Cipher is (NONE) Secure Renegotiation IS NOT supported Compression: NONE Expansion: NONE --- ```Explicit SSLv3 # openssl s_client -connect centinel1000.cardinalcommerce.com:443 -showcerts -ssl3 CONNECTED(0003) depth=2 C = US, O = thawte, Inc., OU = Certification Services Division, OU = (c) 2006 thawte, Inc. - For authorized use only, CN = thawte Primary Root CA verify error:num=20:unable to get local issuer certificate verify return:0 --- Certificate chain 0 s:/C=US/ST=Ohio/L=Mentor/O=CardinalCommerce Corporation/CN=*.cardinalcommerce.com i:/C=US/O=Thawte, Inc./CN=Thawte SSL CA -BEGIN CERTIFICATE- MIIEqjCCA5KgAwIBAgIQfI2U+db8heb8kd3m/BmmITANBgkqhkiG9w0BAQUFADA8 MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMVGhhd3RlLCBJbmMuMRYwFAYDVQQDEw1U aGF3dGUgU1NMIENBMB4XDTEzMDMxOTAwMDAwMFoXDTE1MDQxODIzNTk1OVowdTEL MAkGA1UEBhMCVVMxDTALBgNVBAgTBE9oaW8xDzANBgNVBAcUBk1lbnRvcjElMCMG A1UEChQcQ2FyZGluYWxDb21tZXJjZSBDb3Jwb3JhdGlvbjEfMB0GA1UEAxQWKi5j YXJkaW5hbGNvbW1lcmNlLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC ggEBAMUnIwZ0yEJa80hN4sta/wbr04ogq9XwlY7V7iWiLlfoP/wfpccPt/282+AN oySwuxMWE5EPHC54WXjCowoj3Kdq7fuH11R6DBoXGfuhIJ9l9L187hEPPk6bLq3H F1diHFxGYT0zCNshm7w7Qe/LmQ8N0WSUs21KuB/WZxEts7sIYi4xY/Ig1Mbt6dVV
[Touch-packages] [Bug 1346766] [NEW] Chinese in Ubuntu Touch should use Heiti style sans serif font
Public bug reported: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy-microhei. Below I will list out the pros and cons. I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). Upstream has not updated wqy- microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. Advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font, the downside is it may be of lower quality than DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. Another option is DroidSansFallbackFull.ttf, which is in the fonts-droid package. The advantage is it has coverage of CJK ext. A [1], which wqy- microhei does not provide. On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-meta” package in Ubuntu: New Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). Upstream has not updated wqy- microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. Advantage of wqy- microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font, the downside is it may be of lower quality than DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. Another option is DroidSansFallbackFull.ttf, which is in the fonts- droid package. The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1346766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346455] Re: Launcher overlaps desktop icons on high-res screens
Thanks, seems like an issue with nautilus rather though (using the wrong marging) ** Package changed: unity (Ubuntu) = nautilus (Ubuntu) ** Changed in: nautilus (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1346455 Title: Launcher overlaps desktop icons on high-res screens Status in “nautilus” package in Ubuntu: New Bug description: When using the scaling factor for Unity in Ubuntu 14.04 the desktop icons to the left of the screen are partially covered by the launcher. I'm attaching a screenshot of the issue when using a scaling factor of 2.0. The icons have been placed there using the Organize desktop by name function. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Är en katalog: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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 Date: Mon Jul 21 20:44:02 2014 DistUpgraded: 2014-04-21 16:21:56,686 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GeForce GT 650M [1043:2141] InstallationDate: Installed on 2013-10-18 (275 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: ASUSTeK COMPUTER INC. UX51VZH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=19e47641-ad38-44f7-a159-ce49728e097d ro persistent quiet splash elevator=deadline pcie_aspm=force i915.semaphores=1 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-21 (91 days ago) dmi.bios.date: 03/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX51VZH.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX51VZH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX51VZH.206:bd03/06/2013:svnASUSTeKCOMPUTERINC.:pnUX51VZH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX51VZH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX51VZH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jul 21 19:33:55 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1346455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345505] Re: lock scren leaks keystrokes to window behind greeter
** Tags added: lockscreen -- 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/1345505 Title: lock scren leaks keystrokes to window behind greeter Status in “unity” package in Ubuntu: New Bug description: When my machine comes out of suspend, I am shown the lightdm greeter. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346766] Re: Chinese in Ubuntu Touch should use Heiti style sans serif font
** Description changed: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy-microhei. Below I will list out the pros and cons. I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). Upstream has not updated wqy- microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. Advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font, the downside is it may be of lower quality than DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. Another option is DroidSansFallbackFull.ttf, which is in the fonts-droid package. The advantage is it has coverage of CJK ext. A [1], which wqy- microhei does not provide. On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. + Just a few days ago, Google released the Noto Sans CJK fonts. The + advantage of Noto is it takes care of different writing standard of + Traditional and Simplified Chinese. As a result the total file size is + much bigger. I haven't tried it on Ubuntu Touch so not sure how well it + renders. It's not yet available in fonts-noto [3]. + [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A + [2] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 + [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-meta” package in Ubuntu: New Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). Upstream has not updated wqy- microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. Advantage of wqy- microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font, the downside is it may be of lower quality than DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. Another option is DroidSansFallbackFull.ttf, which is in the fonts- droid package. The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. Just a few days ago, Google released the Noto Sans CJK fonts. The advantage of Noto is it takes care of different writing standard of Traditional and Simplified Chinese. As a result the total file size is much bigger. I haven't tried it on Ubuntu Touch so not sure how well it renders. It's not yet available in fonts-noto [3]. [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A [2] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1346766/+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 1343069] Re: Order of imports and method calls alters API
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Package changed: gtk+3.0 (Ubuntu) = ubuntu ** Changed in: ubuntu Importance: Undecided = Low -- 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/1343069 Title: Order of imports and method calls alters API Status in Ubuntu: New Bug description: Using the python gi.repository (gir1.2-gtk-3.0) if I import Gdk make a specific method call and then import GdkX11 the API for GdkX11 is different than if I had imported both before the method call. To reproduce: Run the script found here (details in comments): http://pastebin.ubuntu.com/7801425/ - Running the script without any arguments passed (i.e. the API is as expected) - Running it with any arguments will make the script call 'Gdk.get_default_root_window()' before the import of GdkX11 meaning the call of 'GdkX11.X11Window.foreign_new_for_display(...)' will fail with the message: AttributeError: type object 'gtk.gdk.X11Window' has no attribute 'foreign_new_for_display' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1343069/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346723] Re: Cannot delete my chroot.
** Also affects: qtcreator-plugin-ubuntu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1346723 Title: Cannot delete my chroot. Status in Click packages: New Status in “click” package in Ubuntu: New Status in “qtcreator-plugin-ubuntu” package in Ubuntu: New Bug description: I found that my install chroot did not appear when I tried to manage my kits to add the build for it. The started to delete it. However, I found that I could not delete it, and it gave me the error. To manage notifications about this bug go to: https://bugs.launchpad.net/click/+bug/1346723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329014] Re: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all
+ type asym
+ playback.pcm {
type hooks
slave.pcm {
type hw
card $CARD
}
hooks.0 {
type ctl_elems
hook_args [
+ }
+ capture.pcm {
+ type hw
+ card $CARD
+}
--
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/1329014
Title:
[Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all
Status in “alsa-driver” package in Ubuntu:
Incomplete
Bug description:
newage@newage-desktop:~$ aplay -l
Lista PLAYBACK de dispozitive
placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 0: emu10k1 [ADC
Capture/Standard PCM Playback]
subdispozitive: 32/32
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
Subdispozitiv #8: subdevice #8
Subdispozitiv #9: subdevice #9
Subdispozitiv #10: subdevice #10
Subdispozitiv #11: subdevice #11
Subdispozitiv #12: subdevice #12
Subdispozitiv #13: subdevice #13
Subdispozitiv #14: subdevice #14
Subdispozitiv #15: subdevice #15
Subdispozitiv #16: subdevice #16
Subdispozitiv #17: subdevice #17
Subdispozitiv #18: subdevice #18
Subdispozitiv #19: subdevice #19
Subdispozitiv #20: subdevice #20
Subdispozitiv #21: subdevice #21
Subdispozitiv #22: subdevice #22
Subdispozitiv #23: subdevice #23
Subdispozitiv #24: subdevice #24
Subdispozitiv #25: subdevice #25
Subdispozitiv #26: subdevice #26
Subdispozitiv #27: subdevice #27
Subdispozitiv #28: subdevice #28
Subdispozitiv #29: subdevice #29
Subdispozitiv #30: subdevice #30
Subdispozitiv #31: subdevice #31
placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 2: emu10k1 efx
[Multichannel Capture/PT Playback]
subdispozitive: 8/8
Subdispozitiv #0: subdevice #0
Subdispozitiv #1: subdevice #1
Subdispozitiv #2: subdevice #2
Subdispozitiv #3: subdevice #3
Subdispozitiv #4: subdevice #4
Subdispozitiv #5: subdevice #5
Subdispozitiv #6: subdevice #6
Subdispozitiv #7: subdevice #7
placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 3: emu10k1 [Multichannel
Playback]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
placa 0: Audigy2 [SB Audigy 2 [SB0240]], dispozitiv 4: p16v [p16v]
subdispozitive: 1/1
Subdispozitiv #0: subdevice #0
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: newage 2071 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jun 11 20:38:53 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-06-11 (0 days ago)
InstallationMedia: It
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audigy2 failed
Symptom_Card: SB0240 Audigy 2 Platinum 6.1 - SB Audigy 2 [SB0240]
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: newage 2071 F pulseaudio
Symptom_Type: No sound at all
Title: [Audigy2 - SB Audigy 2 [SB0240], playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/31/2005
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BZ87510A.86A.0125.P34.0503312215
dmi.board.name: D875PBZ
dmi.board.vendor: Intel Corporation
dmi.board.version: AAC26680-205
dmi.chassis.type: 2
dmi.modalias:
dmi:bvnIntelCorp.:bvrBZ87510A.86A.0125.P34.0503312215:bd03/31/2005:svn:pn:pvr:rvnIntelCorporation:rnD875PBZ:rvrAAC26680-205:cvn:ct2:cvr:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1329014/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346723] Re: Cannot delete my chroot.
Thanks for your bugreport. The part that is failing is the umount after the chroot got cleaned. This part is done by the share/qtcreator/ubuntu/scripts/click_destroy_target in the qtcreator- plugin-ubuntu tree (see lines 33pp of the script). So I simply reassigning to click without any further explanation does not look correct and I added a qtcreator-plugin-ubuntu task back. However I think that all the script should have to do is to run click destory, the fact that it has to do extra lifting is a bug in click IMO so I keep a task for click open. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1346723 Title: Cannot delete my chroot. Status in Click packages: New Status in “click” package in Ubuntu: New Status in “qtcreator-plugin-ubuntu” package in Ubuntu: New Bug description: I found that my install chroot did not appear when I tried to manage my kits to add the build for it. The started to delete it. However, I found that I could not delete it, and it gave me the error. To manage notifications about this bug go to: https://bugs.launchpad.net/click/+bug/1346723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340604] Re: [phone] crash files are only uploaded on boot
Stellar work, guys. I do find it odd that this is causing whoopsie to sit around doing nothing, given that online_state defaults to true, but let's assume for a minute that dbus is indeed the problem. The upstart job doesn't have any non-runlevel service dependencies, so it could conceivably come up before the system bus is started. Coming up before Network Manager should be okay, thanks to dbus service activation. If we cannot talk to Network Manager, we assume Internet connectivity. This covers the case where NetworkManager or DBus have caught fire. Besides, if we cannot submit a crash file, we'll find out pretty quickly. However, this code was written before whoopsie was running on phones and I now worry we could end up in a situation where we're trying to send lots of large crash files on a 3G or paid connection. As much as it pains me to add runtime dependencies to whoopsie, perhaps we should solve this by putting 'start on started dbus' and 'stop on stopping dbus' in the upstart job. What do you guys think? Brian? Does this fix the bug for you, Paul and Joe? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1340604 Title: [phone] crash files are only uploaded on boot Status in “whoopsie” package in Ubuntu: New Bug description: On the phone (mako utopic #125) it seems that crash files are only uploaded on boot and not when the crash occurs. whoopsie is running but doesn't seem to detect that a crash file is ready for upload. = Test Case = 1. In a shell run: $ bash -c 'kill -SEGV $$' 2. Wait until the file _bin_bash.32011.uploaded is created - Check that after a moment whoopsie-upload-all is running - Check the progress of the upload in /var/log/upstart/apport-noui.log - Upon upload, check that /var/log/syslog contains a OOPS entry from whoopsie = Actual Result = whoopsie-upload-all times out and the crash file is not uploaded. If the device is rebooted, the crash is uploaded immediately. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: whoopsie 0.2.34 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu2 Architecture: armhf CrashReports: 640:32011:114:63916:2014-07-11 10:44:24.101108181 +0200:2014-07-11 10:44:07.613514715 +0200:/var/crash/_bin_bash.32011.crash 644:32011:114:0:2014-07-11 10:44:24.101108181 +0200:2014-07-11 10:44:24.101108181 +0200:/var/crash/_bin_bash.32011.upload Date: Fri Jul 11 10:45:02 2014 InstallationDate: Installed on 2014-07-11 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140711-020204) RelatedPackageVersions: apport-noui 2.14.4-0ubuntu2 SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1340604/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345447] Re: [Asus Sabertooth 990FX R2.0, Realtek ALC892 [1002:4383] ] No sound at all
I checked in MS Windows 8.1, there is also no sound. Close this bug please. -- 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/1345447 Title: [Asus Sabertooth 990FX R2.0, Realtek ALC892 [1002:4383] ] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: [SBx00 Azalia (Intel HDA) [1002:4383] ] No sound at all ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ssnake 1445 F pulseaudio /dev/snd/controlC0: ssnake 1445 F pulseaudio CurrentDesktop: Unity Date: Sun Jul 20 08:30:00 2014 HibernationDevice: RESUME=UUID=bf5e716d-81bc-4875-88c7-a1fd5e99fc93 InstallationDate: Installed on 2014-07-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e27bf184-3549-40db-97cf-afe0e929ea22 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1345447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1344047] Re: /usr/lib/arm-linux-gnueabihf/indicator-location/indicator-location-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1
** Tags added: avengers qa-touch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1344047 Title: /usr/lib/arm-linux-gnueabihf/indicator-location/indicator-location- service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most Status in “indicator-location” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-location. This problem was most recently seen with version 13.10.0+14.10.20140612-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/7fbb29cd16437f0b85c68abcc20d4d0b6cea0c13 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1344047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346766] Re: Chinese in Ubuntu Touch should use Heiti style sans serif font
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-meta” package in Ubuntu: Confirmed Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. fonts-droid (DroidSansFallbackFull.ttf, original): - Pros: - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. -Cons: - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. As an additional alternative, just a few days ago, Google released the Noto Sans CJK fonts [2][3]: fonts-noto (Noto Sans CJK fonts): - Pros: - It takes care of different writing standard of Traditional and Simplified Chinese - It covers Korean as well - Cons: - Needs to be tested - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese - Not yet packaged [3] [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A [2] http://googledevelopers.blogspot.de/2014/07/noto-cjk-font-that-is-complete.html [3] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1346766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346766] Re: Chinese in Ubuntu Touch should use Heiti style sans serif font
** Description changed: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy-microhei. Below I will list out the pros and cons. - I am not too much in favour of using wqy-microhei, the reason being that - it is basically a font that based on the Droid font - (DroidSansFallbackFull.ttf to be exact). Upstream has not updated wqy- - microhei for long time, so it lacks any new updates from the Droid font, - although it may not be obvious to users. Advantage of wqy-microhei being - its wider codepoint coverage, for example it also contains Japanese - Kanas and Korean Hanguls in one font, the downside is it may be of lower - quality than DroidSansFallbackFull.ttf due to its lack of maintenance in - recent years. + wqy-microhei (DroidSansFallbackFull.ttf, modified): + - Pros: + - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. + - Cons: + - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). + - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. + - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. - Another option is DroidSansFallbackFull.ttf, which is in the fonts-droid - package. The advantage is it has coverage of CJK ext. A [1], which wqy- - microhei does not provide. On the other hand, wqy-microhei has added - some glyphs that the droid font does not provide, I don't have the exact - number of that but I believe it's just a small number. The disadvantage - is it does not include Korean Hangul, which can be remedied with another - Korean font, and it's not our current concern anyway. + fonts-droid (DroidSansFallbackFull.ttf, original): + - Pros: + - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. + -Cons: + - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. + - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. - Another possible disadvantage of wqy-microhei is it includes more latin - characters, which may result to inconsistent glyphs being used. + As an additional alternative, just a few days ago, Google released the + Noto Sans CJK fonts [2][3]: - Just a few days ago, Google released the Noto Sans CJK fonts. The - advantage of Noto is it takes care of different writing standard of - Traditional and Simplified Chinese. As a result the total file size is - much bigger. I haven't tried it on Ubuntu Touch so not sure how well it - renders. It's not yet available in fonts-noto [3]. + fonts-noto (Noto Sans CJK fonts): + - Pros: + - It takes care of different writing standard of Traditional and Simplified Chinese + - It covers Korean as well + - Cons: + - Needs to be tested + - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese + - Not yet packaged [3] [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A - [2] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 - [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 + [2] http://googledevelopers.blogspot.de/2014/07/noto-cjk-font-that-is-complete.html + [3] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 + [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-meta” package in Ubuntu: Confirmed Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider
[Touch-packages] [Bug 1346815] [NEW] lxc-clone causes duplicate MAC address and IP address
Public bug reported:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
Expected result:
2 container will have different MAC and IP address each other.
Actual result:
2 container will have duplicate MAC and IP address.
# grep lxc.network.hwaddr /var/lib/lxc/{foo,bar}/config
/var/lib/lxc/foo/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
/var/lib/lxc/bar/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
$ sudo lxc-ls -f
NAME STATEIPV4 IPV6 GROUPS AUTOSTART
-
bar RUNNING 10.0.7.60 - - NO
foo RUNNING 10.0.7.60 - - NO
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lxc 1.1.0~alpha1-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 22 17:56:44 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-19 (64 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apparmor apport-bug utopic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1346815
Title:
lxc-clone causes duplicate MAC address and IP address
Status in “lxc” package in Ubuntu:
New
Bug description:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
Expected result:
2 container will have different MAC and IP address each other.
Actual result:
2 container will have duplicate MAC and IP address.
# grep lxc.network.hwaddr /var/lib/lxc/{foo,bar}/config
/var/lib/lxc/foo/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
/var/lib/lxc/bar/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
$ sudo lxc-ls -f
NAME STATEIPV4 IPV6 GROUPS AUTOSTART
-
bar RUNNING 10.0.7.60 - - NO
foo RUNNING 10.0.7.60 - - NO
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lxc 1.1.0~alpha1-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 22 17:56:44 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-19 (64 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1346815/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346766] Re: Chinese in Ubuntu Touch should use Heiti style sans serif font
** Description changed: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy-microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. + - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). - - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. - - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. + - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). + - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. + - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. fonts-droid (DroidSansFallbackFull.ttf, original): - Pros: - - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. + - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. -Cons: - - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. - - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. + - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. + - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. As an additional alternative, just a few days ago, Google released the Noto Sans CJK fonts [2][3]: fonts-noto (Noto Sans CJK fonts): - Pros: - - It takes care of different writing standard of Traditional and Simplified Chinese - - It covers Korean as well + - It takes care of different writing standard of Traditional and Simplified Chinese + - It covers Japanese and Korean as well - Cons: - - Needs to be tested - - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese - - Not yet packaged [3] + - Needs to be tested + - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese + - Not yet packaged [3] [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A [2] http://googledevelopers.blogspot.de/2014/07/noto-cjk-font-that-is-complete.html [3] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-meta” package in Ubuntu: Confirmed Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - I am not too much in
[Touch-packages] [Bug 1346723] Re: Cannot delete my chroot.
** Branch linked: lp:~mvo/click/lp1346723-chroot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1346723 Title: Cannot delete my chroot. Status in Click packages: New Status in “click” package in Ubuntu: New Status in “qtcreator-plugin-ubuntu” package in Ubuntu: New Bug description: I found that my install chroot did not appear when I tried to manage my kits to add the build for it. The started to delete it. However, I found that I could not delete it, and it gave me the error. To manage notifications about this bug go to: https://bugs.launchpad.net/click/+bug/1346723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346819] Re: Running unity8 autopilot tests gets aborted with 'g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async r
The relevant logs are present in: http://ci.ubuntu.com/smokeng/utopic/touch/mako/143:20140722:20140717.1/9195/unity8/1401785/ -- 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/1346819 Title: Running unity8 autopilot tests gets aborted with 'g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error- quark, 0). Exiting.' error Status in “unity8” package in Ubuntu: New Bug description: Running unity8 AP tests (specifically unity8.shell.tests.test_upstart.UpstartIntegrationTests.test_no_sigstop) sees the following and the testing gets aborted: 06:09:34.549 INFO _logging:41 - Starting test unity8.shell.tests.test_upstart.UpstartIntegrationTests.test_no_sigstop (Native Device) 06:09:34.553 WARNING testcase:112 - No tracing available - install the python-autopilot-trace package! 06:09:34.574 WARNING testcase:159 - Process manager backend unavailable, application snapshot support disabled. 06:09:34.595 WARNING utilities:266 - WARNING: in file /home/phablet/autopilot/unity8/shell/tests/__init__.py, line 148 in setUp This function is deprecated. Please use 'the Touch class to instantiate a device object' instead. 06:09:34.767 WARNING utilities:266 - WARNING: in file /home/phablet/autopilot/unity8/shell/tests/test_upstart.py, line 90 in test_no_sigstop This function is deprecated. Please use 'fixtures.EnvironmentVariable' instead. 06:09:34.777 WARNING utilities:266 - WARNING: in file /home/phablet/autopilot/unity8/shell/tests/test_upstart.py, line 59 in _launch_unity This function is deprecated. Please use 'fixtures.EnvironmentVariable' instead. WARNING: QApplication was not created in the main() thread. Testability driver loaded. Wire protocol version is 1.4. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Terminated === The issue is occurring on both mako and flo. Steps to reproduce: 1. bzr branch lp:ububntu-test-cases/touch 2. cd touch 3. ./scripts/provision.sh -i touch -r 110 -n NETWORK_FILE -w (where network file is your wifi file ) 4. scripts/jenkins.sh -a unity8 -p /tmp/results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1346819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345600] Re: Sudo hangs after resume
Ops, I didn't know that. I've hidden it (can't delete). I have no idea how to reproduce, It happened randomly after a resume and I don't know what triggered it. Here is what I did: - Suspend the PC - Resume - Open a terminal and launch sudo nmcli sleep false (workaround for bug #1252121) No prompt for password or anything, can't retake control of the terminal ( I tried ctrl c, ctrl z, ctrl d) and had to close the gnome-terminal window. I tried opening other terminals and issue others sudo commands and same results. I went into tty1 (ctrl alt F1), logon and tried there, same results. If this happens again, what are some commands that would provide useful information and help debug the problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1345600 Title: Sudo hangs after resume Status in “sudo” package in Ubuntu: Incomplete Bug description: After resuming from a suspend, sudo hangs: doesn't prompt for password, doesn't give an error, does absolutely nothing. The entire terminal is blocked and Ctrl C does nothing. Attached strace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1345600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346804] Re: [dialer] Don't display 'SIM1' if only one SIM is available
** Summary changed: - Don't display 'SIM1' if only one SIM is available + [dialer] Don't display 'SIM1' if only one SIM is available -- 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/1346804 Title: [dialer] Don't display 'SIM1' if only one SIM is available Status in Dialer app for Ubuntu Touch: New Status in Messaging App: New Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: New Status in “messaging-app” package in Ubuntu: New Bug description: The dialer shouldn't display SIM1 (in red) when the phone uses only 1 SIM. (cf screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1346804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341708] Re: wpa_supplicant[1306]: nl80211: send_and_recv-nl_recvmsgs failed: -33
*** This bug is a duplicate of bug 1323089 *** https://bugs.launchpad.net/bugs/1323089 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wpa (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1341708 Title: wpa_supplicant[1306]: nl80211: send_and_recv-nl_recvmsgs failed: -33 Status in “wpa” package in Ubuntu: Confirmed Bug description: Jul 14 15:01:51 caravena-530U3C-530U4C wpa_supplicant[1306]: wlan0: CTRL-EVENT-SCAN-STARTED Jul 14 15:01:57 caravena-530U3C-530U4C wpa_supplicant[1306]: nl80211: send_and_recv-nl_recvmsgs failed: -33 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4 Uname: Linux 3.16.0-3-lowlatency x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 14 15:00:14 2014 InstallationDate: Installed on 2014-04-27 (78 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1341708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1346428] Re: [HDA-Intel - HDA Intel, playback] No sound at all
Am 22.07.2014 05:37, schrieb Daniel Letzeisen: You're still booted into the kernel from 12.04 Kernel release:3.2.0-61-generic-pae Boot into the Trusty kernel and see if sound returns. ** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete Danke Daniel Letzeisen, jetzt muss ich nur noch wissen wie der Trusty kernel zum booten zu bringen ist. Frage : welche Befehle muss ich im Terminal eingeben? -- 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/1346428 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I recently installed ubuntu 14.04 LTS since then there is no sound at all. On the same computer windows XP runs then I have sound! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-61.93-generic-pae 3.2.55 Uname: Linux 3.2.0-61-generic-pae i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klaus 1965 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 21 19:40:58 2014 InstallationDate: Installed on 2012-05-16 (796 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Internes Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klaus 1965 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-07-17 (4 days ago) dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0310 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5GC-MX/1333 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0310:bd12/24/2007:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GC-MX/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: dmi.product.name: System Product Name dmi.product.version: Rev 1.xx dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1346428/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1321958] Re: resize2fs does not start to actually grow an ext4
** Attachment added: resize.1.42.8.debug.gz https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321958/+attachment/4159872/+files/resize.1.42.8.debug.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1321958 Title: resize2fs does not start to actually grow an ext4 Status in “e2fsprogs” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 LTS, all proposed updates done Kernel: 3.13.0-24-generic, Package: e2fsprogs 1.42.9-3ubuntu1, System: Haswell i7, 32GB RAM, LSI SAS 9207-8i HBA and LSI SAS 9211-8i HBA I tried to increse the size of an ext4 filesystem. Old size 20TB, wanted new size 28TB. I tried offline resize with resize2fs -fp /dev/md2 and later online resize using resize2fs -f /dev/md2. In both cases, after giving the command a rezise2fs process is created that uses nearly 100% cpu according to top, but it does not perform any actual resize. It only prints its version and date and then it does not finish for hours. I had it running for more than a day without finishing: root@marvin:~# resize2fs -f /dev/md2 resize2fs 1.42.9 (4-Feb-2014) There is never more terminal output than that. It looks to me that resize2fs hangs in a endless calcualtion or loop or something similar. Some more info about the filesystem: root@marvin:~# tune2fs -l /dev/md2 tune2fs 1.42.9 (4-Feb-2014) Filesystem volume name: data Last mounted on: /media/data01 Filesystem UUID: e3845e15-0336-47ae-8aec-df75acb217c5 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options:user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 305225728 Block count: 4883606400 Reserved block count: 0 Free blocks: 22919919 Free inodes: 302894731 First block: 0 Block size: 4096 Fragment size:4096 Group descriptor size:64 Reserved GDT blocks: 1024 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 2048 Inode blocks per group: 128 RAID stride: 128 RAID stripe width:640 Flex block group size:16 Filesystem created: Fri Sep 20 19:45:01 2013 Last mount time: Tue May 20 02:14:37 2014 Last write time: Tue May 20 02:14:37 2014 Mount count: 3 Maximum mount count: -1 Last checked: Tue May 20 01:34:05 2014 Check interval: 0 (none) Lifetime writes: 34 TB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 Default directory hash: half_md4 Directory Hash Seed: 569ec5fc-4d5e-4639-bef3-42cde5fbe948 Journal backup: inode blocks I did also run an filesystem check: root@marvin:~# e2fsck -vfp /dev/md2 2330890 inodes used (0.76%, out of 305225728) 14882 non-contiguous files (0.6%) 949 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 2317190/13041/651 4868171016 blocks used (99.68%, out of 4883606400) 0 bad blocks 1654 large files 2273776 regular files 57105 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 2330881 files The underlying device is an mdadm RAID6 that was grown from 7 to 9 disks. The growing finished without problems before I tried to increase the ext4 size. Solution: The solution for me was to downgrade to e2fsprogs 1.42.8. Then the resize did work and finished within a few minutes. I got the hint to do so in a forum from an user, who had the same problem and solved it with the older version. I have not tested the new 1.42.10. I think this must be a bug introduced in the e2fsprogs version 1.42.9, because all works as expected with the older version. I hope this
[Touch-packages] [Bug 1321958] Re: resize2fs does not start to actually grow an ext4
This bug also affects me. I have tested the new 1.42.11 but no success. Attached the strace; the debug log is empty for my setup also. In addition I added a strace/debug file of the 1.42.8 which worked. I hope that might be helpful. ** Attachment added: resize.1.42.11.strace https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1321958/+attachment/4159870/+files/resize.1.42.11.strace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1321958 Title: resize2fs does not start to actually grow an ext4 Status in “e2fsprogs” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 LTS, all proposed updates done Kernel: 3.13.0-24-generic, Package: e2fsprogs 1.42.9-3ubuntu1, System: Haswell i7, 32GB RAM, LSI SAS 9207-8i HBA and LSI SAS 9211-8i HBA I tried to increse the size of an ext4 filesystem. Old size 20TB, wanted new size 28TB. I tried offline resize with resize2fs -fp /dev/md2 and later online resize using resize2fs -f /dev/md2. In both cases, after giving the command a rezise2fs process is created that uses nearly 100% cpu according to top, but it does not perform any actual resize. It only prints its version and date and then it does not finish for hours. I had it running for more than a day without finishing: root@marvin:~# resize2fs -f /dev/md2 resize2fs 1.42.9 (4-Feb-2014) There is never more terminal output than that. It looks to me that resize2fs hangs in a endless calcualtion or loop or something similar. Some more info about the filesystem: root@marvin:~# tune2fs -l /dev/md2 tune2fs 1.42.9 (4-Feb-2014) Filesystem volume name: data Last mounted on: /media/data01 Filesystem UUID: e3845e15-0336-47ae-8aec-df75acb217c5 Filesystem magic number: 0xEF53 Filesystem revision #:1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options:user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 305225728 Block count: 4883606400 Reserved block count: 0 Free blocks: 22919919 Free inodes: 302894731 First block: 0 Block size: 4096 Fragment size:4096 Group descriptor size:64 Reserved GDT blocks: 1024 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 2048 Inode blocks per group: 128 RAID stride: 128 RAID stripe width:640 Flex block group size:16 Filesystem created: Fri Sep 20 19:45:01 2013 Last mount time: Tue May 20 02:14:37 2014 Last write time: Tue May 20 02:14:37 2014 Mount count: 3 Maximum mount count: -1 Last checked: Tue May 20 01:34:05 2014 Check interval: 0 (none) Lifetime writes: 34 TB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode:8 Default directory hash: half_md4 Directory Hash Seed: 569ec5fc-4d5e-4639-bef3-42cde5fbe948 Journal backup: inode blocks I did also run an filesystem check: root@marvin:~# e2fsck -vfp /dev/md2 2330890 inodes used (0.76%, out of 305225728) 14882 non-contiguous files (0.6%) 949 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 2317190/13041/651 4868171016 blocks used (99.68%, out of 4883606400) 0 bad blocks 1654 large files 2273776 regular files 57105 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 2330881 files The underlying device is an mdadm RAID6 that was grown from 7 to 9 disks. The growing finished without problems before I tried to increase the ext4 size. Solution: The solution for me was to downgrade to e2fsprogs 1.42.8. Then the resize did work and finished within a few minutes. I got the hint to do so in a forum from an user, who had
[Touch-packages] [Bug 1318997] Re: [clock] Provide a way to change alarm sound
** Summary changed: - Provide a way to change alarm sound + [clock] Provide a way to change alarm sound ** Changed in: ubuntu-ux Assignee: Benjamin Keyser (bjkeyser) = Giorgio Venturi (giorgio-venturi) ** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: ubuntu-ux Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1318997 Title: [clock] Provide a way to change alarm sound Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: New Status in Ubuntu Clock App reboot series: In Progress Status in Ubuntu UX bugs: Triaged Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The alarms API provides to way to set different alarm sounds for every alarm. Let's provide that feature to the users so that they can change the alarm sound while creating an alarm. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1318997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296364] Re: [browser] No option for deleting history and cache
** Summary changed: - No option for deleting history and cache + [browser] No option for deleting history and cache ** Changed in: ubuntu-ux Assignee: Benjamin Keyser (bjkeyser) = Giorgio Venturi (giorgio-venturi) ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1296364 Title: [browser] No option for deleting history and cache Status in Ubuntu UX bugs: Triaged Status in Web Browser App: Confirmed Status in “webbrowser-app” package in Ubuntu: Confirmed Bug description: The only way to do this is by deleting the respective files in /home/phablet/.local/share/webbrowser-app/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1296364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1327091] Re: Ubuntu floating home button
** Changed in: ubuntu-ux Assignee: Ruby Hatem (rh-r) = Benjamin Keyser (bjkeyser) ** Changed in: ubuntu-ux Importance: Undecided = Wishlist ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1327091 Title: Ubuntu floating home button Status in Ubuntu UX bugs: Triaged Status in “unity8” package in Ubuntu: Incomplete Bug description: Since we do not have the hardware keys, I am thinking whether we can have a floating circle (top most) kind of thing like what iPhone has. The feature is called apple floating home button. Tap it, and it pops up a menu to navigate, and a user can drag it to anywhere of the screen if it blocks you. I personally think it is a useful feature to the end users, and it is a convenience. We can use it to navigate to the scope, application, or other pages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1327091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343306] Re: [messaging app] send highlight only from msg body focus
** Changed in: ubuntu-ux Status: Triaged = Fix Committed ** Description changed: image#136 really rather minor usability issue 1. enter text in message body 2. focus change to enter who to send msg to 3. enter phone number manually (i don't know if its the same with contact selection) 4. try to send - it won't had to then change focus back to message body as if to type more, in order to get send button to work + + + + DESIRED RESOLUTION: + After user enters the number/recipient manually he should be able to sent the message even if message input box is not in focus. As long as the input box has content the SEND button has to be enabled. -- 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/1343306 Title: [messaging app] send highlight only from msg body focus Status in Messaging App: New Status in Ubuntu UX bugs: Fix Committed Status in “messaging-app” package in Ubuntu: New Bug description: image#136 really rather minor usability issue 1. enter text in message body 2. focus change to enter who to send msg to 3. enter phone number manually (i don't know if its the same with contact selection) 4. try to send - it won't had to then change focus back to message body as if to type more, in order to get send button to work DESIRED RESOLUTION: After user enters the number/recipient manually he should be able to sent the message even if message input box is not in focus. As long as the input box has content the SEND button has to be enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/messaging-app/+bug/1343306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343280] Re: Assertion failure
** Branch linked: lp:~stolowski/unity-scope-click/remove-assertion-and- old-api-fallback ** Changed in: unity-scope-click (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1343280 Title: Assertion failure Status in “unity-scope-click” package in Ubuntu: In Progress Bug description: Got this after trying to navigate to the store scope: (wasn't showing any results) 2014-07-17 13:54:42,813 - WARNING - WARNING: QApplication was not created in the main() thread. RegistryObject::ScopeProcess::exec(): Process for scope: com.canonical.scopes.clickstore started 2014-07-17 13:55:06,436 - WARNING - QIODevice::read: device not open 2014-07-17 13:55:06,437 - WARNING - Network error: Operation canceled (5) 2014-07-17 13:55:06,438 - WARNING - departments call failed due to network error 2014-07-17 13:55:06,439 - WARNING - bootstrap request failed scoperunner: /build/buildd/unity-scope-click-0.1+14.10.20140714/scope/clickstore/store-query.cpp:314: virtual void click::Query::add_highlights(const SearchReplyProxy, const PackageSet): Assertion `curdep' failed. RegistryObject::ScopeProcess::on_process_death(): Process for scope: clickscope terminated RegistryObject::ScopeProcess::on_process_death(): Process for scope: musicaggregator terminated RegistryObject::ScopeProcess::on_process_death(): Process for scope: mediascanner-music terminated RegistryObject::ScopeProcess::on_process_death(): Process for scope: com.canonical.scopes.clickstore terminated RegistryObject::ScopeProcess: Scope: com.canonical.scopes.clickstore closed unexpectedly. Either the process crashed or was killed forcefully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1343280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1237523] Re: [indicators] messaging menu display Empty! when there are not messages
** Changed in: ubuntu-ux Assignee: Matthew Paul Thomas (mpt) = Daniela Ferrai (dferrai) ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: unity8 Status: Incomplete = New ** Changed in: unity8 (Ubuntu) Status: Incomplete = 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/1237523 Title: [indicators] messaging menu display Empty! when there are not messages Status in Ubuntu UX bugs: Triaged Status in The Unity 8 shell: New Status in “unity8” package in Ubuntu: New Bug description: Please change the text back to what it used to be. No new messages, whatever it was previously or what design wants. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1237523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 939427] Re: [Launcher] Impossible to reveal the launcher with a stylus on a Wacom tablet
** Summary changed: - Impossible to reveal the launcher with a stylus on a Wacom tablet + [Launcher] Impossible to reveal the launcher with a stylus on a Wacom tablet ** Changed in: ubuntu-ux Importance: Undecided = Low ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/939427 Title: [Launcher] Impossible to reveal the launcher with a stylus on a Wacom tablet Status in Ubuntu UX bugs: Triaged Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When i run my Lenovo X200 Tablet in tablet mode, i can't reveal the launcher as it is not possible to push the mouse arrow with a stylus against the edge of the screen as needed by the new reveal behavior. I'm running precise with unity 5.4.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/939427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1322525] Re: [sdk] Button icons can't be colourized
** Summary changed: - Button icons can't be colourized + [sdk] Button icons can't be colourized ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: ubuntu-ui-toolkit Status: Incomplete = New ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Incomplete = New -- 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/1322525 Title: [sdk] Button icons can't be colourized Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Triaged Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: The Button icons are not / can't be colourized, which means if you want to use a Button, its icon will not be colourized. In general I think our icon story is a bit messy... related bug #1284233. I think we should only support the image://theme/foo of specifying icons, and whenever we encounter image://theme in the source, we should disable the shape and colourize based on the palette. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 0.1.46+14.10.20140520-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-1.5-generic 3.15.0-rc5 Uname: Linux 3.15.0-1-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 23 10:36:46 2014 SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1322525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1234982] Re: Keyboard does not auto-hide when no longer needed
** Changed in: ubuntu-ux Assignee: Benjamin Keyser (bjkeyser) = Daniela Ferrai (dferrai) ** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Status: New = Triaged ** Summary changed: - Keyboard does not auto-hide when no longer needed + [osk] Keyboard does not auto-hide when no longer needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1234982 Title: [osk] Keyboard does not auto-hide when no longer needed Status in Ubuntu UI Toolkit: Confirmed Status in Ubuntu UX bugs: Triaged Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: When I have entered the requisite data in a form or text field in an application, and then scroll and click on some other UI element which does not require text entry, the keyboard does not automatically go away. Instead, I must swipe down to close the keyboard, which is very annoying, especially when the keyboard is on top of Flickable elements. Having the keyboard auto-hide when it is no longer needed would be a great improvement to the user experience, as would possibly an explicit close button visible on the keyboard itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1234982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1303262] Re: [dialer app] No reason given for a failed connection
** Also affects: telephony-service 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/1303262 Title: [dialer app] No reason given for a failed connection Status in Dialer app for Ubuntu Touch: Confirmed Status in Telephony Service: New Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: New Bug description: Whenever there's a network error (I think remote line busy, too), the dialer app just closes the in-call screen. There's no sound, no feedback on why the call failed. There should be a corresponding sound and the screen should show the reason in the in-call screen after the proximity sensor deactivates, that times out after a few seconds, or a press on the end-call button. This is somewhat similar to bug #1303260 To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1303262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1234886] Re: [osk] No way to auto-repeat
** Changed in: ubuntu-ux Importance: Undecided = Wishlist ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1234886 Title: [osk] No way to auto-repeat Status in Ubuntu Keyboard: Triaged Status in Ubuntu UX bugs: Triaged Status in “ubuntu-keyboard” package in Ubuntu: Triaged Bug description: Auto repeat doesn't seem to work. If it is a hidden gesture or feature, it is not easily discoverable. $ adb shell system-image-cli -i current build number: 78 device name: mako channel: stable last update: 2013-10-03 13:05:32 version version: 78 version ubuntu: 20131003 version device: 20131002.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1234886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1228707] Re: [osk] Keypad should format dialed numbers
** Summary changed: - Keypad should format dialed numbers + [osk] Keypad should format dialed numbers ** Changed in: ubuntu-ux Assignee: Benjamin Keyser (bjkeyser) = Daniela Ferrai (dferrai) ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Summary changed: - [osk] Keypad should format dialed numbers + [dialler] Keypad should format dialed numbers ** Changed in: ubuntu-ux Assignee: Daniela Ferrai (dferrai) = Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1228707 Title: [dialler] Keypad should format dialed numbers Status in Ubuntu UX bugs: Triaged Status in “dialer-app” package in Ubuntu: New Bug description: On Android , when entering a number in the dialer it is automatically formatted to look like how you would display a phone number rather than as one long string of text. This helps helps the user make sure that they have dialed correctly. This does not happen yet with Ubuntu Touch. Example: Number dialed on Android: (555) 555- Number dialed on Ubuntu: 55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1228707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323855] Re: [osk] key magnifier background not consistent on top row
** Changed in: ubuntu-ux Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1323855 Title: [osk] key magnifier background not consistent on top row Status in Ubuntu Keyboard: Fix Released Status in Ubuntu UX bugs: Fix Released Status in “ubuntu-keyboard” package in Ubuntu: Fix Released Bug description: when pressing a key on the top row of the keyboard, the top half of the magnifier is a different color than the bottom half. looks like it's semi-transparent instead of opaque and the apps color is bleeding through. the key magnifier background color should be consistent regardless of what's behind it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1323855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290958] Re: [sdk] Titles/Subtitles sizes do not match across unity8 and ubuntu-ui-toolkit apps
** Changed in: ubuntu-ux Importance: Medium = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1290958 Title: [sdk] Titles/Subtitles sizes do not match across unity8 and ubuntu-ui- toolkit apps Status in Ubuntu UX bugs: Triaged Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “unity8” package in Ubuntu: New Bug description: Not sure if this is bug in unity8 or the ubuntu-ui-toolkit. See screenshots: Applications and System Settings heading are of different height. More suggestions and System sub-heading are of different height. I believe all ubuntu-ui-toolkit based apps are consistent. This is particularly noticable when doing left edge swipe as both app and home screen are visiable at the same time. Screenshots attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1290958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323855] Re: [osk] key magnifier background not consistent on top row
** Changed in: ubuntu-ux Assignee: Michal Izydorczyk (iamfhero) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1323855 Title: [osk] key magnifier background not consistent on top row Status in Ubuntu Keyboard: Fix Released Status in Ubuntu UX bugs: Fix Released Status in “ubuntu-keyboard” package in Ubuntu: Fix Released Bug description: when pressing a key on the top row of the keyboard, the top half of the magnifier is a different color than the bottom half. looks like it's semi-transparent instead of opaque and the apps color is bleeding through. the key magnifier background color should be consistent regardless of what's behind it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1323855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283826] Re: lightdm hangs after updates
I ran apt-get update today and found the problem is solved! I check the apt history log and find that xdg-utils is updated. Is that the most probable cause? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1283826 Title: lightdm hangs after updates Status in GDM: The Gnome Display Manager: New Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: I've updated today my Trusy Thar installation. I can't login to Unity, with my account, or a guest account. Lightdm hangs after password input, or after I click on the Guest account. Also, I used to auto-login. Now it greets me with the screen where I must input my password. After inputing it, lightdm hangs and I can't login. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Sun Feb 23 23:16:24 2014 InstallationDate: Installed on 2014-01-25 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64+mac (20140115) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=cristi autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1283826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346868] [NEW] Canon MX310 printer hangs when printing LibreOffice Writer doc
Public bug reported: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: New Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
Example LO document used in above test. ** Attachment added: prints-but-hangs-printer.odt https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+attachment/4159903/+files/prints-but-hangs-printer.odt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: New Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
lsusb: Bus 001 Device 007: ID 04a9:1728 Canon, Inc. MX310 ser $ ls -l /dev/usb/lp* /dev/bus/usb/*/* crw-rw-r-- 1 root root 189, 0 Jul 21 19:49 /dev/bus/usb/001/001 crw-rw-r--+ 1 root lp 189, 6 Jul 21 19:49 /dev/bus/usb/001/007 crw-rw-r-- 1 root root 189, 128 Jul 21 19:49 /dev/bus/usb/002/001 crw-rw-r-- 1 root root 189, 132 Jul 21 19:49 /dev/bus/usb/002/005 crw-rw-r-- 1 root root 189, 256 Jul 21 19:49 /dev/bus/usb/003/001 crw-rw-r-- 1 root root 189, 384 Jul 21 19:49 /dev/bus/usb/004/001 crw-rw-r-- 1 root root 189, 512 Jul 21 19:49 /dev/bus/usb/005/001 crw-rw-r-- 1 root root 189, 513 Jul 21 19:49 /dev/bus/usb/005/002 crw-rw-r-- 1 root root 189, 514 Jul 21 19:49 /dev/bus/usb/005/003 crw-rw 1 root lp 180, 0 Jul 21 19:49 /dev/usb/lp0 crw-rw 1 root lp 180, 1 Jul 21 19:49 /dev/usb/lp1 $ sudo usb_printerid /dev/usb/lp0 GET_DEVICE_ID string: MFG:Canon;CMD:BJL,BJRaster3,BSCCe,PLI;SOJ:TXT01;MDL:MX310 series;CLS:PRINTER;DES:Canon MX310 series;VER:1.040;STA:10;HRI:EU;MSI:E3; $ sudo usb_printerid /dev/usb/lp1 GET_DEVICE_ID string: MFG:Canon;CMD:MultiPASS 2.1;MDL:MX310 series FAX;CLS:PRINTER;DES:Canon MX310 series FAX; $ lpinfo -v network https network http network ipp network ipps network socket network lpd network ipp14 direct usb://Canon/MX310%20series?serial=470CDEinterface=1 direct usb://Canon/MX310%20series%20FAX?serial=470CDEinterface=2 direct hp network smb direct hpfax $ Cups 1.7.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: New Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
ports: analog-input-microphone: Микрофон (priority 8700, latency offset 0 usec, available: unknown) properties: device.icon_name = audio-input-microphone analog-input-linein: Линейный вход (priority 8100, latency offset 0 usec, available: unknown) properties: analog-input: Аналоговый вход (priority 8000, latency offset 0 usec, available: unknown) properties: active port: analog-input-microphone Simple mixer control 'Line',0 Capabilities: cswitch cswitch-joined penum Capture channels: Mono Mono: Capture [off] Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 31 Mono: Capture 31 [100%] [12.00dB] [on] Simple mixer control 'Mic Boost (+20dB)',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [off] Simple mixer control 'Mic Source',0 Capabilities: cenum Items: 'Mic Jack' 'Front Panel' Item0: 'Mic Jack' do mic boost really affected playback only ? ARECORD List of CAPTURE Hardware Devices card 0: STX [Xonar STX], device 0: Multichannel [Multichannel] Subdevices: 0/1 Subdevice #0: subdevice #0 it is strange to use multichannel as device name , does it replay support multi channel capture ? you have to ask the author why not implement capture source control to select rear Mic, front mic and line in -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Microphone is not working on frontpanel of my soundcard Asus Xonar Essence STX. In windows it works normally. Ubuntu 13.04 x64 Tested on the latest kernel 3.9-rc8 With 3.8.0 kernel problem is the same. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.0-030900rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simplehuman 2394 F pulseaudio /dev/snd/pcmC0D0c: simplehuman 2394 F...m pulseaudio /dev/snd/controlC1: simplehuman 2394 F pulseaudio Date: Mon Apr 22 15:06:32 2013 InstallationDate: Installed on 2013-02-14 (67 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:STX failed Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia Symptom_Type: None of the above Title: [AV200 - Xonar STX, recording] Recording problem UpgradeStatus: Upgraded to raring on 2013-02-14 (67 days ago) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.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.:bvr1402:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346766] Re: Chinese in Ubuntu Touch should use Heiti style sans serif font
** Description changed: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy-microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. fonts-droid (DroidSansFallbackFull.ttf, original): - Pros: - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. -Cons: - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. As an additional alternative, just a few days ago, Google released the Noto Sans CJK fonts [2][3]: fonts-noto (Noto Sans CJK fonts): - Pros: - It takes care of different writing standard of Traditional and Simplified Chinese - It covers Japanese and Korean as well - Cons: - Needs to be tested - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese - - Not yet packaged [3] + - Not yet packaged [4] [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A [2] http://googledevelopers.blogspot.de/2014/07/noto-cjk-font-that-is-complete.html [3] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-meta” package in Ubuntu: Confirmed Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. fonts-droid (DroidSansFallbackFull.ttf, original): - Pros: - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. -Cons: - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. As an additional alternative, just a few days ago, Google released the Noto Sans CJK fonts [2][3]: fonts-noto (Noto Sans CJK fonts): - Pros: - It takes care of different writing standard of Traditional and Simplified Chinese - It covers Japanese and Korean as well - Cons: - Needs to be tested - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese - Not yet packaged [4] [1]
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
Please follow the instructions of the section USB printer does not print or prints garbage on https://wiki.ubuntu.com/DebuggingPrintingProblems. Thanks. ** Changed in: cups (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: Incomplete Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346868] Re: Canon MX310 printer hangs when printing LibreOffice Writer doc
Thanks for quick response. I did follow as much of that as seemed relevant to me. Can you be more specific? By the way, I had difficulty following the instructions to turn on the error log. The gear icon in 14.04 has no 'Printer' in its menu (and 12.04 has 'Printers', not 'Printer'). Though once I explored 12.04 and realised that the intent was to use the standard dialog in System Settings, I got past that. It's a wiki, but it's an immutable page, so someone needs to fix it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1346868 Title: Canon MX310 printer hangs when printing LibreOffice Writer doc Status in “cups” package in Ubuntu: Incomplete Bug description: New Linux user reports problem printing letters from Lenovo T60 with Linux Mint 17 (Qiana) on Canon MX310 printer using LibreOffice 4.2.4.2. I've borrowed the printer and done a fresh install of Mint 17 and Ubuntu 14.04 and reproduced the problem on both systems. A short letter prints to completion as far as the computer is concerned and is removed from the print queue. The printer prints the full text but does not eject the page, and the display shows PRINTING The paper has to be manually pulled out of the printer and it has to be power cycled to resume normal operation. I will attach the document used. I've turned on the error log, but it's about 14MB, rather large to upload. I'll be returning the printer today, and travelling for perhaps a week, but after that I'm keen to resume investigation, though this is my first time with a printer problem so I'll be appreciating any guidance. In contrast, printing from Firefox and Gedit have not shown any problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: Unity Date: Tue Jul 22 11:52:10 2014 InstallationDate: Installed on 2014-07-14 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lpstat: device for MX310-series: usb://Canon/MX310%20series?serial=470CDEinterface=1 MachineType: LENOVO 1706W5K Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card PpdFiles: MX310-series: Canon MX310 series - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=f88bfaa3-b8a8-4ec0-beaf-cf990a6066cc ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 7BET45WW (1.05 ) dmi.board.name: 1706W5K 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:bvr7BET45WW(1.05):bd04/21/2006:svnLENOVO:pn1706W5K:pvrThinkPadX60:rvnLENOVO:rn1706W5K:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1706W5K dmi.product.version: ThinkPad X60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1346868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345447] Re: [Asus Sabertooth 990FX R2.0, Realtek ALC892 [1002:4383] ] No sound at all
I think this is hardware issue. -- 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/1345447 Title: [Asus Sabertooth 990FX R2.0, Realtek ALC892 [1002:4383] ] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: [SBx00 Azalia (Intel HDA) [1002:4383] ] No sound at all ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ssnake 1445 F pulseaudio /dev/snd/controlC0: ssnake 1445 F pulseaudio CurrentDesktop: Unity Date: Sun Jul 20 08:30:00 2014 HibernationDevice: RESUME=UUID=bf5e716d-81bc-4875-88c7-a1fd5e99fc93 InstallationDate: Installed on 2014-07-19 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e27bf184-3549-40db-97cf-afe0e929ea22 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1345447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283775] Re: Launcher: icon pips are not always updated properly
Today, I installed Ubuntu 14.04 64bit on a spare HDD, and applied all updates. I checked whether the bug still affected the system. It did. After that, I enabled the proposed repository and updated the system. I can also confirm, that the new version of unity fixes the issue (I don't have time for 'long term' testing, but as I see Jorge Morais's results are also promising). -- 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/1283775 Title: Launcher: icon pips are not always updated properly Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] The number of pips next to the Launcher icon may not be accurate and lead the user to believe that the number of open windows for a particular app is not what is true in reality. [Test Case] 1. Open up 2 Firefox windows. 2. Close one of the windows. Pips (the little arrows) next to the Launcher icon should reflect the number of open windows. [Regression potential] None identified. Original Description: Only occurs when there is just 1 app's windows (unmaxed), assumes multiple workspaces is enabled Test case: Open nautilus (1 pip shows up R. click nautilus icon open another nautilus window (a 2nd pip does not show, likely due to Bug 1281816 Drag the 2nd naut window fully into current ws, 2nd pip still not shown Click on Desktop, 2nd pip shows up Close one of the naut windows, icon still shows 2 pips. Click again on Desktop, 2nd pip is then removed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Feb 23 12:28:18 2014 InstallationDate: Installed on 2014-02-22 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140222) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
Is it safe to rename those .desktop files? -- 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/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346896] [NEW] Ubuntu SDK when SSH to device attempts to connect on same port as running webmin (10000)
Public bug reported: When running an Ubuntu SDK QML app on a nexus 4 device the connection is attempting to connect to localhost at port 1. [08:35:49] debug1: Connecting to 127.0.0.1 [127.0.0.1] port 1. debug1: Connection established. debug1: identity file /home/randy/.config/ubuntu-sdk/ubuntudevice_id_rsa type 1 debug1: identity file /home/randy/.config/ubuntu-sdk/ubuntudevice_id_rsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: ssh_exchange_identification: HTTP/1.0 200 Document follows This causes a conflict on my system due to a running webmin program on the same port: debug1: ssh_exchange_identification: Connection: close debug1: ssh_exchange_identification: debug1: ssh_exchange_identification: h1Error - Document follows/h1 [08:35:49] debug1: ssh_exchange_identification: preThis web server is running in SSL mode. Try the URL a href='https://localhost:1/'https://localhost:1//a instead.br/pre [08:35:49] debug1: ssh_exchange_identification: preThis web server is running in SSL mode. Try the URL a href='https://localhost:1/'https://localhost:1//a instead.br/pre [08:35:49] ssh_exchange_identification: Connection closed by remote host This was corrected when I removed 1 from the available ports listed in: Options--Devices--Free Ports Suggestion: remove 1 from the list by default Better: make it more obvious how that port is selected, or allow for choosing port from a list somehow. It took me avery long to figure out that this was the problem. Also, i added -v to the ssh command in the /usr/share/qtcreator/ubuntu/scripts/qtc_device_run_app_click script so that I could get full errors listed in the SDK window. Description:Ubuntu 14.04 LTS Release:14.04 ubuntu-sdk: Installed: 1.126 Candidate: 1.126 Version table: *** 1.126 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New ** Tags: device sdk -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1346896 Title: Ubuntu SDK when SSH to device attempts to connect on same port as running webmin (1) Status in “ubuntu-touch-meta” package in Ubuntu: New Bug description: When running an Ubuntu SDK QML app on a nexus 4 device the connection is attempting to connect to localhost at port 1. [08:35:49] debug1: Connecting to 127.0.0.1 [127.0.0.1] port 1. debug1: Connection established. debug1: identity file /home/randy/.config/ubuntu-sdk/ubuntudevice_id_rsa type 1 debug1: identity file /home/randy/.config/ubuntu-sdk/ubuntudevice_id_rsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: ssh_exchange_identification: HTTP/1.0 200 Document follows This causes a conflict on my system due to a running webmin program on the same port: debug1: ssh_exchange_identification: Connection: close debug1: ssh_exchange_identification: debug1: ssh_exchange_identification: h1Error - Document follows/h1 [08:35:49] debug1: ssh_exchange_identification: preThis web server is running in SSL mode. Try the URL a href='https://localhost:1/'https://localhost:1//a instead.br/pre [08:35:49] debug1: ssh_exchange_identification: preThis web server is running in SSL mode. Try the URL a href='https://localhost:1/'https://localhost:1//a instead.br/pre [08:35:49] ssh_exchange_identification: Connection closed by remote host This was corrected when I removed 1 from the available ports listed in: Options--Devices--Free Ports Suggestion: remove 1 from the list by default Better: make it more obvious how that port is selected, or allow for choosing port from a list somehow. It took me avery long to figure out that this was the problem. Also, i added -v to the ssh command in the /usr/share/qtcreator/ubuntu/scripts/qtc_device_run_app_click script so that I could get full errors listed in the SDK window. Description: Ubuntu 14.04 LTS Release: 14.04 ubuntu-sdk: Installed: 1.126 Candidate: 1.126 Version table: *** 1.126 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1346896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346819] Re: Unity8 non-upstart tests fight for hardware with unity-system-compositor
The upstart tests in unity8 don't actually use upstart, meaning that unity8 and u-s-c fight for hardware. ** Summary changed: - Running unity8 autopilot tests gets aborted with 'g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.' error + Unity8 non-upstart tests fight for hardware with unity-system-compositor ** Changed in: unity8 (Ubuntu) Status: New = Confirmed ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Michał Sawicz (saviq) ** Changed in: unity8 (Ubuntu) Status: Confirmed = 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/1346819 Title: Unity8 non-upstart tests fight for hardware with unity-system- compositor Status in “unity8” package in Ubuntu: In Progress Bug description: Running unity8 AP tests (specifically unity8.shell.tests.test_upstart.UpstartIntegrationTests.test_no_sigstop) sees the following and the testing gets aborted: 06:09:34.549 INFO _logging:41 - Starting test unity8.shell.tests.test_upstart.UpstartIntegrationTests.test_no_sigstop (Native Device) 06:09:34.553 WARNING testcase:112 - No tracing available - install the python-autopilot-trace package! 06:09:34.574 WARNING testcase:159 - Process manager backend unavailable, application snapshot support disabled. 06:09:34.595 WARNING utilities:266 - WARNING: in file /home/phablet/autopilot/unity8/shell/tests/__init__.py, line 148 in setUp This function is deprecated. Please use 'the Touch class to instantiate a device object' instead. 06:09:34.767 WARNING utilities:266 - WARNING: in file /home/phablet/autopilot/unity8/shell/tests/test_upstart.py, line 90 in test_no_sigstop This function is deprecated. Please use 'fixtures.EnvironmentVariable' instead. 06:09:34.777 WARNING utilities:266 - WARNING: in file /home/phablet/autopilot/unity8/shell/tests/test_upstart.py, line 59 in _launch_unity This function is deprecated. Please use 'fixtures.EnvironmentVariable' instead. WARNING: QApplication was not created in the main() thread. Testability driver loaded. Wire protocol version is 1.4. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Terminated === The issue is occurring on both mako and flo. Steps to reproduce: 1. bzr branch lp:ububntu-test-cases/touch 2. cd touch 3. ./scripts/provision.sh -i touch -r 110 -n NETWORK_FILE -w (where network file is your wifi file ) 4. scripts/jenkins.sh -a unity8 -p /tmp/results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1346819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346804] Re: [dialer] Don't display 'SIM1' if only one SIM is available
** Branch linked: lp:~tiagosh/dialer-app/hide-accounts-switcher ** Branch linked: lp:~tiagosh/messaging-app/hide-accounts-switcher -- 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/1346804 Title: [dialer] Don't display 'SIM1' if only one SIM is available Status in Dialer app for Ubuntu Touch: New Status in Messaging App: New Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: New Status in “messaging-app” package in Ubuntu: New Bug description: The dialer shouldn't display SIM1 (in red) when the phone uses only 1 SIM. (cf screenshot) To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1346804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319149] Re: [HP Pavilion 11-n038ca x360 PC] Boots very unreliably
@Scott Ashcroft, Can you please make a guide how to to that for other users? I don' t have the knowledge to do it all by my self. Thanks, Bart -- 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/1319149 Title: [HP Pavilion 11-n038ca x360 PC] Boots very unreliably Status in “linux” package in Ubuntu: Incomplete Status in “xorg” package in Ubuntu: Confirmed Bug description: Boots very unreliably. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rick 1911 F pulseaudio CurrentDesktop: Unity Date: Tue May 13 14:47:04 2014 HibernationDevice: RESUME=UUID=bd1e0db9-24a6-4fb7-a9c0-32c457348b08 InstallationDate: Installed on 2014-05-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=5fb0f2a1-a777-4483-81cf-b488d59fc309 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2209 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd02/15/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097512405F00010420180:rvnHewlett-Packard:rn2209:rvr57.19:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 11 x360 PC dmi.product.version: 097512405F00010420180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1319149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299778] Re: After resume from suspend, could not enter password to unlock
Can confirm, happening also in arch Linux with whatever greeter I choose. Can't input after second suspend either. I just get no input screen and the cursor is not present until I move it or press any key. It just flashes with interaction and goes away. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1299778 Title: After resume from suspend, could not enter password to unlock Status in “lightdm” package in Ubuntu: Confirmed Bug description: I could move the mouse but not enter a password, it was just like the keyboard was dead. Switched to vt8 I got a login to another users session. I could type in the password box there. Then back to vt7 and I was able to enter the password to unlock. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.13-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 30 16:26:34 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-28 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1299778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1255889] Re: [system settings] Disabling scope online search in systemsettings makes it impossible to install new apps
** Changed in: unity-scope-click (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1255889 Title: [system settings] Disabling scope online search in systemsettings makes it impossible to install new apps Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Triaged Status in “unity-scope-click” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: New Bug description: The heated discussions regarding the online search capabilities in the Dash have led to the possibility to disable that in through systemsettings which many people use. On Touch, this introduces the problem that a user cannot browse/install any new apps any more. I think there is the need to have a dedicated application for the app store which allows to find and install new apps without having to enable full Dash online search capabilities. - Desired resolution: - In the new Unity8 Dash architecture, there is no longer a global search, users choose which lens they would like to search before performing a search. This means the issue privacy issue from Unity7 is no longer present, therefore this setting can be removed from System Settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1255889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346687] Re: Ubuntu 14 KVM Guest I/O Elevator Non-configurable
Your other distributions are running older kernels. This behavior was changed in the kernel because it does not make sense to run an elevator on virtual devices. You will notice the same thing on bare metal for lvm and raid: they no longer have their own elevator. Instead the IO is passed straight down the stack to the real disk where there is a single elevator managing all IO to that disk, whether it comes from different virtual machines, or logical volumes. ** Changed in: util-linux (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1346687 Title: Ubuntu 14 KVM Guest I/O Elevator Non-configurable Status in “util-linux” package in Ubuntu: Invalid Bug description: Ubuntu 14.04 guest runs pretty much standard standard configuration: KVM hypervisor, ACPI and APIC enabled, virtio disk bus, raw storage format... While running this project, I am also involved in testing SSD drives across different Linux distributions and their support for discard option (TRIM). To cut the story short, Ubuntu-based KVM guest did not set any scheduler on the boot disk vda): # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk 1 0B 0B vda1 part 1 0B 0B vda2 part 1 0B 0B vda5 part 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B That is in stark contrast with other distributions running almost identical KVM guest configuration (with the exception of the root file system using BTRFS instead of EXT4 on SUSE). Oracle Linux 6.5: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk deadline 1 0B 0B vda1 part deadline 1 0B 0B vda2 part deadline 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B OpenSUSE 13.1: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom cfq 1 0B 0B vda disk cfq 1 0B 0B vda1 part cfq 1 0B 0B vda2 part cfq 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B Indeed, checking elevator capabilities for boot disk on Ubuntu KVM guest showed: # cat /sys/block/vda/queue/scheduler none Other Linux distributions show more options: # cat /sys/block/vda/queue/scheduler noop deadline [cfq] As well, attempts to change the elevator on Ubuntu guest fail. For example: # echo noop /sys/block/vda/queue/scheduler # echo $? 0 # cat /sys/block/vda/queue/scheduler none Setting it globally in /etc/default/grub and updating it via update- grub2 fails too. In the meantime, to automate check of elevators (schedulers) and discard support for SSD drives and thin-provisioned volumes on Linux, I wrote simple Perl script: http://www.circlingcycle.com.au/Unix-sources/Linux-check-IO-scheduler- and-discard-support.pl.txt Part of the results on RHEL 6.5 server would look like: INFO: I/O elevator (scheduler) and discard support summary INFO: Hard Disk sdb configured with I/O scheduler cfq INFO: SSD sda configured with I/O scheduler deadline supports discard operation INFO: Hard Disk sdc configured with I/O scheduler cfq INFO: Hard Disk sdi configured with I/O scheduler cfq INFO: Hard Disk sdh configured with I/O scheduler cfq The Ubuntu KVM guest runs latest paches: Linux ubuntu14-vm2.circlingcycle.com.au 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Regards, Dusan Baljevic VK2COT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1346687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1069964 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Unable to mount Blank CD-R disc. Location is already mounted. Status in “glib2.0” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1069964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346687] Re: Ubuntu 14 KVM Guest I/O Elevator Non-configurable
** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1346687 Title: Ubuntu 14 KVM Guest I/O Elevator Non-configurable Status in “util-linux” package in Ubuntu: Invalid Bug description: Ubuntu 14.04 guest runs pretty much standard standard configuration: KVM hypervisor, ACPI and APIC enabled, virtio disk bus, raw storage format... While running this project, I am also involved in testing SSD drives across different Linux distributions and their support for discard option (TRIM). To cut the story short, Ubuntu-based KVM guest did not set any scheduler on the boot disk vda): # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk 1 0B 0B vda1 part 1 0B 0B vda2 part 1 0B 0B vda5 part 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B That is in stark contrast with other distributions running almost identical KVM guest configuration (with the exception of the root file system using BTRFS instead of EXT4 on SUSE). Oracle Linux 6.5: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom deadline 1 0B 0B vda disk deadline 1 0B 0B vda1 part deadline 1 0B 0B vda2 part deadline 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B OpenSUSE 13.1: # lsblk -io KNAME,TYPE,SCHED,ROTA,DISC-GRAN,DISC-MAX KNAME TYPE SCHED ROTA DISC-GRAN DISC-MAX sr0 rom cfq 1 0B 0B vda disk cfq 1 0B 0B vda1 part cfq 1 0B 0B vda2 part cfq 1 0B 0B dm-0 lvm 1 0B 0B dm-1 lvm 1 0B 0B Indeed, checking elevator capabilities for boot disk on Ubuntu KVM guest showed: # cat /sys/block/vda/queue/scheduler none Other Linux distributions show more options: # cat /sys/block/vda/queue/scheduler noop deadline [cfq] As well, attempts to change the elevator on Ubuntu guest fail. For example: # echo noop /sys/block/vda/queue/scheduler # echo $? 0 # cat /sys/block/vda/queue/scheduler none Setting it globally in /etc/default/grub and updating it via update- grub2 fails too. In the meantime, to automate check of elevators (schedulers) and discard support for SSD drives and thin-provisioned volumes on Linux, I wrote simple Perl script: http://www.circlingcycle.com.au/Unix-sources/Linux-check-IO-scheduler- and-discard-support.pl.txt Part of the results on RHEL 6.5 server would look like: INFO: I/O elevator (scheduler) and discard support summary INFO: Hard Disk sdb configured with I/O scheduler cfq INFO: SSD sda configured with I/O scheduler deadline supports discard operation INFO: Hard Disk sdc configured with I/O scheduler cfq INFO: Hard Disk sdi configured with I/O scheduler cfq INFO: Hard Disk sdh configured with I/O scheduler cfq The Ubuntu KVM guest runs latest paches: Linux ubuntu14-vm2.circlingcycle.com.au 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Regards, Dusan Baljevic VK2COT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1346687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346957] [NEW] Remove entries for departments db
Public bug reported: Once all the preinstalled apps provide the X-Ubuntu-Default-Department- ID in their desktop files, we should remove them from the initial database. Also, the tool for re-creating the database needs to be updated to not populate pkgmap with installed click apps. ** Affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1346957 Title: Remove entries for departments db Status in “unity-scope-click” package in Ubuntu: New Bug description: Once all the preinstalled apps provide the X-Ubuntu-Default- Department-ID in their desktop files, we should remove them from the initial database. Also, the tool for re-creating the database needs to be updated to not populate pkgmap with installed click apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1346957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342694] Re: qmlscene crashed with SIGSEGV in _M_release() on quit
Fix committed into lp:mir/devel at revision None, scheduled for release
in mir, milestone Unknown
** Changed in: mir
Status: In Progress = Fix Committed
--
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/1342694
Title:
qmlscene crashed with SIGSEGV in _M_release() on quit
Status in Mir:
Fix Committed
Status in Mir 0.5 series:
In Progress
Status in “mir” package in Ubuntu:
Triaged
Status in “qtdeclarative-opensource-src” package in Ubuntu:
Invalid
Bug description:
Given the app:
import Ubuntu.Components 1.1
MainView {
applicationName: blah
Button {
anchors.centerIn: parent
text: Quit
onClicked: Qt.quit()
}
}
And launching it with:
$ qmlscene test.qml
--desktop_file_hint=/usr/share/applications/webbrowser-app.desktop
on the phone (sorry for the webbrowser part, bug #1325984).
On pressing Quit, the app segfaults.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: qmlscene 5.3.0-3ubuntu7
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.4-0ubuntu2
Architecture: armhf
Date: Wed Jul 16 12:22:05 2014
ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene
ExecutableTimestamp: 1404724229
InstallationDate: Installed on 2014-07-15 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf
(20140715-115453)
ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene test.qml
--desktop_file_hint=/usr/share/applications/webbrowser-app.desktop
ProcCwd: /home/phablet
Signal: 11
SourcePackage: qtdeclarative-opensource-src
StacktraceTop:
MirConnection::~MirConnection() () from
/usr/lib/arm-linux-gnueabihf/libmirclient.so.8
MirConnection::~MirConnection() () from
/usr/lib/arm-linux-gnueabihf/libmirclient.so.8
mir_connection_release () from /usr/lib/arm-linux-gnueabihf/libmirclient.so.8
?? () from
/usr/lib/arm-linux-gnueabihf/libubuntu_application_api_touch_mirclient.so.2.1.0
Title: qmlscene crashed with SIGSEGV in MirConnection::~MirConnection()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty
video
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1342694/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346954] [NEW] Accounts list scrolls over header
You have been subscribed to a public bug: Add multiple accounts in system settings online accounts. 8 or more required to trigger issue. As you scroll the top entry overlaps the header rather than the header scrolling off screen. See photo. Seen on mako # 133 and 144. ** Affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New -- Accounts list scrolls over header https://bugs.launchpad.net/bugs/1346954 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings-online-accounts in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316005] Re: Panel shadow appears over full screen applications w/ locally integrated menus enabled
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1316005 Title: Panel shadow appears over full screen applications w/ locally integrated menus enabled Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] An ugly Panel shadow can be drawn over full screen windows which is visually unappealing. [Test Case] 1. Enable local menus. System Settings-Appearance-Behavior and then select In the window's title bar in the Show the menus for a window section. 2. Open an image in Image Viewer 3. Double click the image to full-screen it 4. Move the mouse to the top of the screen to access the controls [Regression Potential] None identified. Original Description: The shadow of the top Unity panel draws over full screen applications that have controls visible when the mouse is moved. Steps to reproduce: 1) Open an image in Image Viewer 2) Double click the image to full-screen it 3) Move the mouse to the top of the screen to access the controls Expected behavior: Only the image and the Image Viewer controls should be visible Acutal behavior: The Unity panel shadow is drawn on top of the controls at the top of the screen Notes: This also appears in the Videos application, but does not in VLC or gimp. I believe it is GTK applications with UI elements that only appear on mouse movement (gimp's UI is static, and I believe VLC is Qt based). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64
[Touch-packages] [Bug 1317348] Re: Switcher (Alt-Tab) does not respect monitor-defined scaling factor
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1317348 Title: Switcher (Alt-Tab) does not respect monitor-defined scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. [Test case] 1. From Unity Control Center - Displays - Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice). 2. Open some windows and press Alt+Tab 3. Both Switcher icons, application names and spreaded windows (when pressing down, or right-clicking on an icon) decorations should be scaled to match the selected scaling factor. In Multi-monitor scenario it should match the scaling factor of the monitor where the view opens (so where the mouse is). [Regression potential]The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313280] Re: Fullscreen window set to Always on Top in single-monitor will hide the lockscreen
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1313280 Title: Fullscreen window set to Always on Top in single-monitor will hide the lockscreen Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] A fullscreen window set to always on top hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to Always on Top (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L (5) The lockscreen should go above the Totem window now. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. [Regression Potential]Two cases may potentially source regressions. (1) windows that need to appear above the lockscreen, such as on-screen keyboards,(2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. (3) Indicator menus might be not being drawn To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1320438] Re: Unity launcher auto hide fails on screen unlock using Super+L
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1320438 Title: Unity launcher auto hide fails on screen unlock using Super+L Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] The launcher is not properly auto-hidden when locking the screen using Super+L keybinding [Test case] 1. From Unity Control Center - Appearance - Behavior enable the launcher auto-hiding 2. Press Super+L in order to lock the screen 3. Unlock the screen, now the launcher should be hidden [Regression potential] Unity might hang when locking the screen (due to the sync compiz call to screen-getCurrentTime() that in some very-rare cases in the past demonstrated to be prone to some race conditions). No case has been recorded so far in this scenario, though. - I use a Compaq cq40 running Trusty. If I lock the screen using the Super+L hotkey, upon unlocking the unity launcher bar appears on the screen. I'll have to press Super key twice to hide it again (Hitting once brings up the dash home, hitting once again hides the launcher). This is not observed if use the Ctrl+Alt+L hotkey. The following are the system details: @Enigma:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04 LTS Release: 14.04 Codename: trusty @Enigma:~$ uname -a Linux Enigma 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:31:42 UTC 2014 i686 i686 i686 GNU/Linux @Enigma:~$ sudo apt-cache policy unity unity: Installed: 7.2.0+14.04.20140423-0ubuntu1.2 Candidate: 7.2.0+14.04.20140423-0ubuntu1.2 Version table: ***
[Touch-packages] [Bug 1308323] Re: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1308323 Title: Shutdown/reboot/login/logout dialogs not scaled after toggling UI scale Edit Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: 1. Install Ubuntu-trusty image and boot into OS 2. Go to System settings Display 3. Toggle UI scale up or down 4. Press power button to launch poweroff notification prompt 5. Check if the contents of the prompt is also scaled in accordance to the UI scale settings [Expected results] Contents of the poweroff notification prompt should be scaled in accordance to the UI scale settings [Actual results] Contents of the poweroff notification prompt is not scaled [Inpact] When Caps lock was active the icon did not render a tooltip if you moused over the icon. This can be consfusing if the user has no clue what the icon means. [Test case] 1) Go to System Settings - Display 2) Change the DPI scale to a noticable size. 3) Then select Shutdown to bring up the Dialog. Expected Result: The shutdown dialog scaled correctly. [Regression potential] Low. Worse case we just dont scale, the changes are pretty isolated to the number changing game. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1308323/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310200] Re: Indicators disappear at the panel (clementine, dropbox, skype etc)
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1310200 Title: Indicators disappear at the panel (clementine, dropbox, skype etc) Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some indicators icons (such as skype, clementine, dropbox) disappear from panel when changing graphical state. [Test case] 1. Run one of the affected software (i.e. skype) 2. The skype icon should show in the unity panel 3. Change your status in skype to something else (i.e. Away) 4. The skype icon in the panel should change without disappearing [Regression potential] Nothing known, the icons database is reloaded for safety checks and this does nothing but updating the icons. Unconstant indicators (which are changig their graphical state during work of the app, for example skype, clemetine) disappears on the panel. They appear again if you click the mouse on th closest rightest indicator and pull it into left side or they appear after some time. ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Apr 20 12:26:14 2014 InstallationDate: Installed on 2014-01-14 (95 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)SourcePackage: unity UpgradeStatus: Upgraded to trusty on
[Touch-packages] [Bug 607796] Update Released
The verification of the Stable Release Update for compiz has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. *** SRU debdiff links *** The Unity SRU debdiff for this can be found at https://launchpadlibrarian.net/180013321/unity-7.2.2-trusty-sru.debdiff. The Compiz SRU debdiff for this can be found at https://launchpadlibrarian.net/180013356/compiz-0.9.11.2-trusty- sru.debdiff ### Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as buggybutclosed for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken
This bug was fixed in the package compiz - 1:0.9.11.2+14.04.20140714-0ubuntu1 --- compiz (1:0.9.11.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Chris Townsend ] * Bump version to 0.9.11.2. [ Marco Trevisan (Treviño) ] * Scale: use XShape extension to exclude dnd input in the screen-parts outside workArea This will work property also in multi-monitor, without requiring multiple X windows for each output device. Also don't terminate the scale unless a drag-n-drop action is not really over. Add a spinner that shows up over a window, during the DnD timeout. Plus, make sure we terminate the scale without focusing the selected icon when cancelling it and some code cleanup (LP: #607796) (LP: #727904) (LP: #1308112) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:36:56 + ** Changed in: compiz (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/727904 Title: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Confirmed Bug description: To reproduce: Open two Chrome windows and two Firefox windows. Drag a .html file over the Chrome icon in the Launcher. A spread of the two Chrome windows should appear. Then continue the same drag, and drag the file over the Firefox icon in the Launcher. Nothing happens, the Chrome spread is still displayed. Desired behaviour; After a spread appears as a result of the user dragging a file over a application icon in the Launcher, if the user then drags the file over a different application icon (where the application is also a valid drop receptacle for the file type) the spread should switch to the newly selected application. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299975] Re: wireless script checks wrong sys file
This bug was fixed in the package pm-utils - 1.4.1-13ubuntu0.1 --- pm-utils (1.4.1-13ubuntu0.1) trusty-proposed; urgency=medium * debian/patches/17-fix-wireless-hook.patch: Fix typo in wireless hook (LP: #1299975). -- Whoopie whoopi...@gmx.net Tue, 08 Jul 2014 07:49:28 +0200 ** Changed in: pm-utils (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1299975 Title: wireless script checks wrong sys file Status in “pm-utils” package in Ubuntu: Fix Released Status in “pm-utils” source package in Trusty: Fix Released Bug description: TEST CASE: - on a machine with a wireless interface, run: PM_FUNCTIONS=/usr/lib/pm-utils/functions sh -ex /usr/lib/pm-utils/power.d/wireless true and verify that it fails with /sys/class/net/wlan0/device/enable: No such file or directory - install the update and run the command again and verify that the script continue beyond the point it stopped earlier, i.e. that it stops at a later point when running e.g. iwconfig - now powersaving for wireless via pm-utils should work as intended from the script REGRESSION POTENTIAL: - the functionality in the script was completely broken before, by fixing this bug any bug in the power management that were previously hidden may now be uncovered. On Trusty (beta), while trying to diagnose an issue with the wireless not connecting upon resume from standby, I discovered an invalid check in '/usr/lib/pm-utils/power.d/wireless'. The script checks '/sys/class/net/$1/device/enable' to see if the wireless device is enabled, failing to perform any configuration if this sys file does not exist. That happens to be the case for me (intel wireless), which the actual location is '/sys/class/net/$1/device/enabled' (enable - enabled). Changing the script to use the correct location has not fixed my wireless resume issue, but perhaps it is contributing to wireless issues for others. My wireless power-saving is correctly turned off upon resume now, though (it would get stuck in power-saving mode sometimes). $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ apt-cache policy pm-utils pm-utils: Installed: 1.4.1-13 Candidate: 1.4.1-13 Version table: *** 1.4.1-13 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1299975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281058] Re: [UIFe] The system shutdowns when multiple accounts are open
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1281058 Title: [UIFe] The system shutdowns when multiple accounts are open Status in Ayatana Design: Fix Committed Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “indicator-session” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Fix Released Status in “indicator-session” source package in Trusty: New Status in “systemd” source package in Trusty: New Status in “unity” source package in Trusty: Fix Released Status in “unity-greeter” source package in Trusty: Fix Released Bug description: [Impact] Other users logged into a system may loose work if another user shuts down/reboots a system. Data loss is not a Good Thing. [Test Case] Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost [ Regression Potential] None. -- Desired resolution: - Add a warning message informing the user that other users are logged in and then shutting down will also close their sessions as proposed in the mockup attached to comment #12 - The warning message should be Other users are currently logged in to this computer, shutting down now will also close these other sessions To
[Touch-packages] [Bug 1346958] Re: Can't add multiple twitter accounts in one session
** Package changed: ubuntu-system-settings (Ubuntu) = ubuntu-system- settings-online-accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1346958 Title: Can't add multiple twitter accounts in one session Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: New Bug description: On mako 133 and 144 I can't add multiple twitter accounts in one session Add twitter account, first one adds fine. Go back to accounts list and add another When you get authed by twitter and get the redirecting back to application the accounts dialog dies. At that point you can't add another until you kill system settings Had this on my devel 133 and proposed 144 phones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1346958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346958] [NEW] Can't add multiple twitter accounts in one session
You have been subscribed to a public bug: On mako 133 and 144 I can't add multiple twitter accounts in one session Add twitter account, first one adds fine. Go back to accounts list and add another When you get authed by twitter and get the redirecting back to application the accounts dialog dies. At that point you can't add another until you kill system settings Had this on my devel 133 and proposed 144 phones ** Affects: ubuntu-system-settings-online-accounts (Ubuntu) Importance: Undecided Status: New -- Can't add multiple twitter accounts in one session https://bugs.launchpad.net/bugs/1346958 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings-online-accounts in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343905] Update Released
The verification of the Stable Release Update for upstart has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1343905 Title: Empty desktop in Xubuntu 14.04 on reboot after upgrading upstart package Status in “upstart” package in Ubuntu: Fix Released Status in “upstart” source package in Trusty: Fix Released Status in “upstart” source package in Utopic: Fix Released Bug description: Recently I've setup fresh Xubuntu 14.04 and upgraded system to current state. After reboot and logon to system I've got empty desktop and mouse pointer with no panels and icons. Alt+F2 and similar key combinations didn't work. Switching to console by Ctrl+Alt+F1 worked. After short investigation I've downgraded upstart to version 1.12.1-0ubuntu4 and rebooted. Now everything works as expected. The .xsession-errors log form empty desktop session attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1343905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343905] Re: Empty desktop in Xubuntu 14.04 on reboot after upgrading upstart package
This bug was fixed in the package upstart - 1.12.1-0ubuntu4.2 --- upstart (1.12.1-0ubuntu4.2) trusty; urgency=medium * Safe guard against SESSIONTYPE-less sessions. (LP: #1343905) upstart (1.12.1-0ubuntu4.1) trusty; urgency=medium [ James Hunt ] LP: #1317727 * debian/manpages/upstart-events.7: Correction for 'rotate-logs'. * debian/upstart.cron.daily: Specify full path to initctl. * init/man/init.8: Add missing information on '--chroot-sessions'. * debian/upstart.apport: Sort system and session jobs. [ Iain Lane ] * xsession-init: Set $GNOME_DESKTOP_SESSION_ID if we are launching a gnome-session session. Some applications (Qt4) require this to be set to any value to detect the environment in use. It was historically set by gnome-session but now this is no longer the root of the session so not all user processes are guaranteed to have it. (LP: #1305294) [ Dimitri John Ledkov ] * Cherrypick reboot command fix to not process REBOOTCOMMAND argument when in runlevels 2-5 and without using force flag. (LP: #1174272) -- Dimitri John Ledkov x...@ubuntu.com Fri, 18 Jul 2014 10:27:27 +0100 ** Changed in: upstart (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1343905 Title: Empty desktop in Xubuntu 14.04 on reboot after upgrading upstart package Status in “upstart” package in Ubuntu: Fix Released Status in “upstart” source package in Trusty: Fix Released Status in “upstart” source package in Utopic: Fix Released Bug description: Recently I've setup fresh Xubuntu 14.04 and upgraded system to current state. After reboot and logon to system I've got empty desktop and mouse pointer with no panels and icons. Alt+F2 and similar key combinations didn't work. Switching to console by Ctrl+Alt+F1 worked. After short investigation I've downgraded upstart to version 1.12.1-0ubuntu4 and rebooted. Now everything works as expected. The .xsession-errors log form empty desktop session attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1343905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305294] Update Released
The verification of the Stable Release Update for upstart has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1305294 Title: QT uses incorrect theme when GNOME_DESKTOP_SESSION_ID is unset Status in “upstart” package in Ubuntu: Fix Released Status in “upstart” source package in Trusty: Fix Released Bug description: [ Description ] When launching Qt applications from indicators under Unity, the theme isn't right. [ Fix ] It's because GNOME_DESKTOP_SESSION_ID is unset due to problems in upstart scripts. Qt uses this to decide whether to apply the GTK theme. Fix is to set this as early as possible, in Upstart's xsession- init job. [ Regression potential ] We're setting the environment variable ~all the time in the session. Maybe something could be expecting it not to be set? [ QA ] This is a bit racy, so you might not see it all the time. Install vlc, restart your session (or the sound indicator), then click the indicator and launch vlc. You might see the wrong theme before and should always see the right theme after. [ Original description ] Bug discovered when launching VLC from the sound indicator applet: the QT UI theme is wrong. The theme is correct when launched from Unity launcher or terminal. Please see the attached screenshots. I've tracked it down to a difference in environment in the VLC process: When launched from indicator-sound, the variable GNOME_DESKTOP_SESSION_ID is unset, and this causes VLC to become themed incorrectly. (If the variable is given any value, then VLC looks correct.) To reproduce, either: 1) Launch VLC from indicator-sound (make sure it's not already running and has been started from somewhere else) 2) Or just start VLC like this from terminal: $ GNOME_DESKTOP_SESSION_ID= vlc Looks like a bug in qt4, which seems to depend on GNOME_DESKTOP_SESSION_ID being set [to anything] to pick up the correct theme. (The variable is deprecated, according to its default value in Ubuntu 14.04.) Try: $ GNOME_DESKTOP_SESSION_ID= qtconfig Observe theme not picked up from Desktop settings in qtconfig. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qt4-qtconfig 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 22:15:27 2014 InstallationDate: Installed on 2014-04-01 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: qt4-x11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1305294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1174272] Re: 'reboot now' reverting to maintenance mode, instead of rebooting
This bug was fixed in the package upstart - 1.12.1-0ubuntu4.2 --- upstart (1.12.1-0ubuntu4.2) trusty; urgency=medium * Safe guard against SESSIONTYPE-less sessions. (LP: #1343905) upstart (1.12.1-0ubuntu4.1) trusty; urgency=medium [ James Hunt ] LP: #1317727 * debian/manpages/upstart-events.7: Correction for 'rotate-logs'. * debian/upstart.cron.daily: Specify full path to initctl. * init/man/init.8: Add missing information on '--chroot-sessions'. * debian/upstart.apport: Sort system and session jobs. [ Iain Lane ] * xsession-init: Set $GNOME_DESKTOP_SESSION_ID if we are launching a gnome-session session. Some applications (Qt4) require this to be set to any value to detect the environment in use. It was historically set by gnome-session but now this is no longer the root of the session so not all user processes are guaranteed to have it. (LP: #1305294) [ Dimitri John Ledkov ] * Cherrypick reboot command fix to not process REBOOTCOMMAND argument when in runlevels 2-5 and without using force flag. (LP: #1174272) -- Dimitri John Ledkov x...@ubuntu.com Fri, 18 Jul 2014 10:27:27 +0100 ** Changed in: upstart (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1174272 Title: 'reboot now' reverting to maintenance mode, instead of rebooting Status in Upstart: Fix Released Status in “upstart” package in Ubuntu: Fix Released Status in “upstart” source package in Trusty: Fix Released Bug description: [Impact] * reboot(8) command has behaviour different from the documented one, in particular when passing optional REBOOTCOMMAND argument, whilst not in runlevel 0 or 6 and without passing --force, shutdown(8) was not invoked with the appropriate arguments. Actual behaviour was dropping to runlevel 1, instead of the expected reboot. [Test Case] * Whilst booted normally to runlevel 2, after executing: $ sudo reboot please * machine should complete reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1174272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317727] Re: documentation corrections, apport hook fixups
This bug was fixed in the package upstart - 1.12.1-0ubuntu4.2 --- upstart (1.12.1-0ubuntu4.2) trusty; urgency=medium * Safe guard against SESSIONTYPE-less sessions. (LP: #1343905) upstart (1.12.1-0ubuntu4.1) trusty; urgency=medium [ James Hunt ] LP: #1317727 * debian/manpages/upstart-events.7: Correction for 'rotate-logs'. * debian/upstart.cron.daily: Specify full path to initctl. * init/man/init.8: Add missing information on '--chroot-sessions'. * debian/upstart.apport: Sort system and session jobs. [ Iain Lane ] * xsession-init: Set $GNOME_DESKTOP_SESSION_ID if we are launching a gnome-session session. Some applications (Qt4) require this to be set to any value to detect the environment in use. It was historically set by gnome-session but now this is no longer the root of the session so not all user processes are guaranteed to have it. (LP: #1305294) [ Dimitri John Ledkov ] * Cherrypick reboot command fix to not process REBOOTCOMMAND argument when in runlevels 2-5 and without using force flag. (LP: #1174272) -- Dimitri John Ledkov x...@ubuntu.com Fri, 18 Jul 2014 10:27:27 +0100 ** Changed in: upstart (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1317727 Title: documentation corrections, apport hook fixups Status in “upstart” package in Ubuntu: Fix Released Status in “upstart” source package in Trusty: Fix Released Status in “upstart” source package in Utopic: Fix Released Bug description: [impact] * miscellaneous changes in upstart SRU to trusty: * debian/manpages/upstart-events.7: Correction for 'rotate-logs'. * debian/upstart.cron.daily: Specify full path to initctl. * init/man/init.8: Add missing information on '--chroot-sessions'. * debian/upstart.apport: Sort system and session jobs. manpages - update to be factually correct with behavior seen in trusty-release upstart. sort upstart jobs in the apport hook, for easy of comparison/diffing during report aggregation and analysis. use the system initctl to emit rotate-logs event. [testcases] * file ubuntu-bug against upstart, check that running jobs attachment has all jobs sorted * inspect manpages to render correctly describe correct behaviour * check that rotate-logs event is emitted daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1317727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1174272] Update Released
The verification of the Stable Release Update for upstart has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1174272 Title: 'reboot now' reverting to maintenance mode, instead of rebooting Status in Upstart: Fix Released Status in “upstart” package in Ubuntu: Fix Released Status in “upstart” source package in Trusty: Fix Released Bug description: [Impact] * reboot(8) command has behaviour different from the documented one, in particular when passing optional REBOOTCOMMAND argument, whilst not in runlevel 0 or 6 and without passing --force, shutdown(8) was not invoked with the appropriate arguments. Actual behaviour was dropping to runlevel 1, instead of the expected reboot. [Test Case] * Whilst booted normally to runlevel 2, after executing: $ sudo reboot please * machine should complete reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1174272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305294] Re: QT uses incorrect theme when GNOME_DESKTOP_SESSION_ID is unset
This bug was fixed in the package upstart - 1.12.1-0ubuntu4.2 --- upstart (1.12.1-0ubuntu4.2) trusty; urgency=medium * Safe guard against SESSIONTYPE-less sessions. (LP: #1343905) upstart (1.12.1-0ubuntu4.1) trusty; urgency=medium [ James Hunt ] LP: #1317727 * debian/manpages/upstart-events.7: Correction for 'rotate-logs'. * debian/upstart.cron.daily: Specify full path to initctl. * init/man/init.8: Add missing information on '--chroot-sessions'. * debian/upstart.apport: Sort system and session jobs. [ Iain Lane ] * xsession-init: Set $GNOME_DESKTOP_SESSION_ID if we are launching a gnome-session session. Some applications (Qt4) require this to be set to any value to detect the environment in use. It was historically set by gnome-session but now this is no longer the root of the session so not all user processes are guaranteed to have it. (LP: #1305294) [ Dimitri John Ledkov ] * Cherrypick reboot command fix to not process REBOOTCOMMAND argument when in runlevels 2-5 and without using force flag. (LP: #1174272) -- Dimitri John Ledkov x...@ubuntu.com Fri, 18 Jul 2014 10:27:27 +0100 ** Changed in: upstart (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1305294 Title: QT uses incorrect theme when GNOME_DESKTOP_SESSION_ID is unset Status in “upstart” package in Ubuntu: Fix Released Status in “upstart” source package in Trusty: Fix Released Bug description: [ Description ] When launching Qt applications from indicators under Unity, the theme isn't right. [ Fix ] It's because GNOME_DESKTOP_SESSION_ID is unset due to problems in upstart scripts. Qt uses this to decide whether to apply the GTK theme. Fix is to set this as early as possible, in Upstart's xsession- init job. [ Regression potential ] We're setting the environment variable ~all the time in the session. Maybe something could be expecting it not to be set? [ QA ] This is a bit racy, so you might not see it all the time. Install vlc, restart your session (or the sound indicator), then click the indicator and launch vlc. You might see the wrong theme before and should always see the right theme after. [ Original description ] Bug discovered when launching VLC from the sound indicator applet: the QT UI theme is wrong. The theme is correct when launched from Unity launcher or terminal. Please see the attached screenshots. I've tracked it down to a difference in environment in the VLC process: When launched from indicator-sound, the variable GNOME_DESKTOP_SESSION_ID is unset, and this causes VLC to become themed incorrectly. (If the variable is given any value, then VLC looks correct.) To reproduce, either: 1) Launch VLC from indicator-sound (make sure it's not already running and has been started from somewhere else) 2) Or just start VLC like this from terminal: $ GNOME_DESKTOP_SESSION_ID= vlc Looks like a bug in qt4, which seems to depend on GNOME_DESKTOP_SESSION_ID being set [to anything] to pick up the correct theme. (The variable is deprecated, according to its default value in Ubuntu 14.04.) Try: $ GNOME_DESKTOP_SESSION_ID= qtconfig Observe theme not picked up from Desktop settings in qtconfig. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qt4-qtconfig 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 9 22:15:27 2014 InstallationDate: Installed on 2014-04-01 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) SourcePackage: qt4-x11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1305294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
This bug was fixed in the package compiz - 1:0.9.11.2+14.04.20140714-0ubuntu1 --- compiz (1:0.9.11.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Chris Townsend ] * Bump version to 0.9.11.2. [ Marco Trevisan (Treviño) ] * Scale: use XShape extension to exclude dnd input in the screen-parts outside workArea This will work property also in multi-monitor, without requiring multiple X windows for each output device. Also don't terminate the scale unless a drag-n-drop action is not really over. Add a spinner that shows up over a window, during the DnD timeout. Plus, make sure we terminate the scale without focusing the selected icon when cancelling it and some code cleanup (LP: #607796) (LP: #727904) (LP: #1308112) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:36:56 + ** Changed in: compiz (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. *** SRU debdiff links *** The Unity SRU debdiff for this can be found at https://launchpadlibrarian.net/180013321/unity-7.2.2-trusty-sru.debdiff. The Compiz SRU debdiff for this can be found at https://launchpadlibrarian.net/180013356/compiz-0.9.11.2-trusty- sru.debdiff ### Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as buggybutclosed for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304882] Re: [Regression] Launcher doesn't reappear fully after hiding from DND
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1304882 Title: [Regression] Launcher doesn't reappear fully after hiding from DND Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] A user can get into a situation where the Launcher is no longer available. This can lead to frustration and loss of productivity. [Test Case] 1. Set Launcher into auto-hide mode. 2. Drag a file over the Launcher. 3. Keep moving the dragged file to the left edge where you see the Launcher hide again. 4. Cancel the drag operation. 5. Move mouse cursor over to the Launcher to reveal it. Launcher should be fully revealed. [Regression Potential] The Launcher will hide again when you keep moving a file over to the left. However, this is not a regression as this behavior was present before this bug was fixed, so no new regressions are identified. Original Description: Dragging a file to the launcher and keeping it there causes the launcher to hide after a timeout. The problem: The launcher either doesn't reappear or only slide in by a few pixels. A screencast is attatched to showcase the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1304882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) Status: New = 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/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the
[Touch-packages] [Bug 1299975] Update Released
The verification of the Stable Release Update for pm-utils has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1299975 Title: wireless script checks wrong sys file Status in “pm-utils” package in Ubuntu: Fix Released Status in “pm-utils” source package in Trusty: Fix Released Bug description: TEST CASE: - on a machine with a wireless interface, run: PM_FUNCTIONS=/usr/lib/pm-utils/functions sh -ex /usr/lib/pm-utils/power.d/wireless true and verify that it fails with /sys/class/net/wlan0/device/enable: No such file or directory - install the update and run the command again and verify that the script continue beyond the point it stopped earlier, i.e. that it stops at a later point when running e.g. iwconfig - now powersaving for wireless via pm-utils should work as intended from the script REGRESSION POTENTIAL: - the functionality in the script was completely broken before, by fixing this bug any bug in the power management that were previously hidden may now be uncovered. On Trusty (beta), while trying to diagnose an issue with the wireless not connecting upon resume from standby, I discovered an invalid check in '/usr/lib/pm-utils/power.d/wireless'. The script checks '/sys/class/net/$1/device/enable' to see if the wireless device is enabled, failing to perform any configuration if this sys file does not exist. That happens to be the case for me (intel wireless), which the actual location is '/sys/class/net/$1/device/enabled' (enable - enabled). Changing the script to use the correct location has not fixed my wireless resume issue, but perhaps it is contributing to wireless issues for others. My wireless power-saving is correctly turned off upon resume now, though (it would get stuck in power-saving mode sometimes). $ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 $ apt-cache policy pm-utils pm-utils: Installed: 1.4.1-13 Candidate: 1.4.1-13 Version table: *** 1.4.1-13 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1299975/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307738] Re: Lockscreen caps lock icon drawn under text entry, should be a white icon.
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1307738 Title: Lockscreen caps lock icon drawn under text entry, should be a white icon. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: Lockscreen caps lock icon drawn under text entry, should be a white icon. [Inpact] The old Caps lock icon was rendering below the Text Entry causeing it to grey out. This is hard to see. [Test case] 1) Press Super + L (lockscreen) 2) Press Caps Lock (unless its already active) Expected Result: White Caps lock icon. [Regression potential] Very low, worse case the icon doesn't render correctly, yeilding a grey icon. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346428] Re: [HDA-Intel - HDA Intel, playback] No sound at all
Hold right shift key during boot to access grub menu.. -- 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/1346428 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I recently installed ubuntu 14.04 LTS since then there is no sound at all. On the same computer windows XP runs then I have sound! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-61.93-generic-pae 3.2.55 Uname: Linux 3.2.0-61-generic-pae i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klaus 1965 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 21 19:40:58 2014 InstallationDate: Installed on 2012-05-16 (796 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Internes Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: klaus 1965 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: Upgraded to trusty on 2014-07-17 (4 days ago) dmi.bios.date: 12/24/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0310 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5GC-MX/1333 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev x.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: Rev 1.xx dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0310:bd12/24/2007:svnSystemmanufacturer:pnSystemProductName:pvrRev1.xx:rvnASUSTeKComputerINC.:rnP5GC-MX/1333:rvrRevx.xx:cvnASUSTekComputerINC.:ct3:cvrRev1.xx: dmi.product.name: System Product Name dmi.product.version: Rev 1.xx dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1346428/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1309739] Re: Unity launcher icon edge illumination is offset
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1309739 Title: Unity launcher icon edge illumination is offset Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Many users tend to change the size of the Launcher icons to better fit the screen resolution of their monitor or for personal tastes and workflow reasons. This issue causes the edge glow of icons to be offset at sizes less than 40 and greater than 56. This looks really ugly and unprofessional. [Test case] * Open CCSM-Ubuntu Unity Plugin-Launcher * Change Launcher Icon Backlight Mode to Edge Illumination Toggles * Change Launcher Icon Size to some value in the range described above such as 38. * Make sure an application is open on the Launcher to see the edge glow around the icon. [Regression Potential] The texture itself may not look as nice on hi DPI screens when rescaling, but when the texture is offset from the icon, it would be hard to tell anyways. Original Description: In Unity, when using the edge illumination effect on launcher icons is offset. It shows to the top and left of the icons, but barely at all to the right and bottom. This was not a problem before Trusty; in Saucy and previous releases the edges were aligned properly. See attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1309739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308911] Re: Clipboard contents are accessible within lockscreen
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) 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 in Ubuntu. https://bugs.launchpad.net/bugs/1308911 Title: Clipboard contents are accessible within lockscreen Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] It's possible to paste clipboard content into the lockscreen text fields [Testcase] 1. Copy some text 2. Lock the screen (Super+L or Ctrl+Alt+L) 3. Try to paste the contents of your clipboard using Ctrl+V into the lockscreen input(s) field. 4. Nothing should be pasted there [Regression Potential] Anything known --- - Copy e.g. my password to the clipboard (highlight and/or Ctrl+C) - Lock the screen (Ctrl+Alt+L) - Paste content from clipboard using middle mouse button or Ctrl+V into input field - Login possible (if copied text was the password) Expected behaviour: No content from clipboard available at all in lockscreen lsb_release -rd: Description: Ubuntu 14.04 LTS Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346815] Re: lxc-clone causes duplicate MAC address and IP address
After installing old packages, it seems a regression between
https://launchpad.net/ubuntu/+source/lxc/1.0.4-0ubuntu2/+build/6098430
and
https://launchpad.net/ubuntu/+source/lxc/1.1.0~alpha1-0ubuntu1/+build/6162946
--
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/1346815
Title:
lxc-clone causes duplicate MAC address and IP address
Status in “lxc” package in Ubuntu:
New
Bug description:
A cloned container will have the same MAC address and IP address with
the original container.
How to reproduce:
1. $ sudo lxc-create -t ubuntu-cloud -n foo -- --release trusty
2. $ sudo lxc-clone foo bar
3. $ sudo lxc-start -d -n foo
4. $ sudo lxc-start -d -n bar
Expected result:
2 container will have different MAC and IP address each other.
Actual result:
2 container will have duplicate MAC and IP address.
# grep lxc.network.hwaddr /var/lib/lxc/{foo,bar}/config
/var/lib/lxc/foo/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
/var/lib/lxc/bar/config:lxc.network.hwaddr = 00:16:3e:d8:d8:78
$ sudo lxc-ls -f
NAME STATEIPV4 IPV6 GROUPS AUTOSTART
-
bar RUNNING 10.0.7.60 - - NO
foo RUNNING 10.0.7.60 - - NO
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lxc 1.1.0~alpha1-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jul 22 17:56:44 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-19 (64 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140518)
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
defaults.conf:
lxc.network.type = veth
lxc.network.link = lxcbr0
lxc.network.flags = up
lxc.network.hwaddr = 00:16:3e:xx:xx:xx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1346815/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 727904] Update Released
The verification of the Stable Release Update for compiz has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/727904 Title: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Confirmed Bug description: To reproduce: Open two Chrome windows and two Firefox windows. Drag a .html file over the Chrome icon in the Launcher. A spread of the two Chrome windows should appear. Then continue the same drag, and drag the file over the Firefox icon in the Launcher. Nothing happens, the Chrome spread is still displayed. Desired behaviour; After a spread appears as a result of the user dragging a file over a application icon in the Launcher, if the user then drags the file over a different application icon (where the application is also a valid drop receptacle for the file type) the spread should switch to the newly selected application. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
This bug was fixed in the package unity - 7.2.2+14.04.20140714-0ubuntu1 --- unity (7.2.2+14.04.20140714-0ubuntu1) trusty; urgency=medium [ Alfred Neumayer ] * Restore the launcher position by reversing the animation and unsetting the DND_PUSHED_OFF quirk. (LP: #1304882) [ Brandon Schaefer ] * TextInput: move the warning icon inside the input field, render it white (LP: #1307738) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * Lockscreen warning icon needs a tooltip to say what the warning is about! (LP: #1308288) [ Marco Trevisan (Treviño) ] * UnityScreen: always paint the lockscreen above, just add menu and onboard as exceptions Some code cleanup, factorizing similar code. (LP: #1313280) * ApplicationLauncherIcon: Focus and, in case, Spread the windows on DnD After 1 second that an user is over an icon, that icon should focus the relative application and Spread its windows if it has more than one opened. Correctly handle the DnD scale in launcher, and apply glow to the icon under pointer. (LP: #607796) * ShutdownView: Scale up the Buttons and Text plus Borders of the UnityWindowView. (LP: #1308323) * SwitcherView: use RawPixel's for the size values and convert them to match current scaling (LP: #1317348) * PluginAdapter: try to grab the screen to make sure that the screen is not grabbed FocusIn event with NotifyGrab mode is not always triggered by X when a window takes the grab, then we need to ensure that there's no grab by trying to get one. We only care about keyboard here, since pointer grabs don't affect us in general. (LP: #741869) * ShortcutView: use RawPixel's for the size values and convert them to match current scaling Plus dinamically allocate horizontal space, not to cut the text. (LP: #924840) [ Chris Townsend ] * Fix issue where scaling the edge illumination up and down with the size of the Launcher icons would cause the illumination border to be offset and smaller than the icon. (LP: #1309739) * Fix issue where the number of Launcher icon pips are not always properly updated when a new window of an already running application is opened. (LP: #1283775) * Fix issue where the Panel shadow would get drawn over drop down windows in full screen windows. (LP: #1316005) * Bump upstream release to 7.2.2. [ Andrea Azzarone ] * Clear the clipboard when locking the screen. (LP: #1308911) * Disable switcher gestures if screen is locked. Fixed a regression. (LP: #1321043) * Pass the correct options to showLauncherKeyTerminate in UnityScreen::OnLockScreen (LP: #1320438) * Fix skype indicator blinking. (LP: #1310200) * Add a warning in the session dialog if other sessions are still open. (LP: #1281058) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 14 Jul 2014 14:31:00 + ** Changed in: unity (Ubuntu Trusty) Status: New = 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/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: New Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Buggy Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. To manage notifications about this bug go to:
[Touch-packages] [Bug 1346383] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@137:collect_info:process_report:mark_report_upload
Here's the Traceback from the crash: Traceback (most recent call last): File /usr/share/apport/whoopsie-upload-all, line 137, in module stamps = collect_info() File /usr/share/apport/whoopsie-upload-all, line 88, in collect_info res = process_report(r) File /usr/share/apport/whoopsie-upload-all, line 71, in process_report apport.fileutils.mark_report_upload(report) File /usr/lib/python3/dist-packages/apport/fileutils.py, line 119, in mark_report_upload with open(upload, 'a'): PermissionError: [Errno 13] Permission denied: '/var/crash/_usr_bin_unity8.32011.upload' -- 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/1346383 Title: /usr/share/apport/whoopsie-upload- all:PermissionError:/usr/share/apport/whoopsie-upload- all@137:collect_info:process_report:mark_report_upload Status in “apport” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.14.4-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/1bba7b68c8ff3370890bc9ebeefcfd7ec0287988 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1346383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324157] Re: cannot receive MMS using AT+T
** Changed in: mobile-broadband-provider-info (Ubuntu)
Status: Triaged = Invalid
** Changed in: ofono (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mobile-broadband-provider-
info in Ubuntu.
https://bugs.launchpad.net/bugs/1324157
Title:
cannot receive MMS using AT+T
Status in Messaging App:
Invalid
Status in “mobile-broadband-provider-info” package in Ubuntu:
Invalid
Status in “network-manager” package in Ubuntu:
Triaged
Status in “nuntium” package in Ubuntu:
New
Status in “ofono” package in Ubuntu:
Fix Released
Bug description:
using build 51
MMS recv support is enabled but I cannot receive any attachments with At+t as
my service provider. I tried with both wifi enabled and disabled
Here are the logs and contexts
phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
MessageProxy = proxy.mobile.att.net
Protocol = ip
Name = ATT Phone
Username =
IPv6.Settings = { }
Active = 0
Settings = { }
MessageCenter = http://mmsc.mobile.att.net
Password =
Type = internet
AccessPointName = phone
[ /ril_0/context2 ]
MessageProxy = wireless.cingular.com
Protocol = ip
Name = ATT WAP
Username =
IPv6.Settings = { }
Active = 0
Settings = { }
MessageCenter = http://mmsc.cingular.com/
Password =
Type = internet
AccessPointName = wap.cingular
[ /ril_0/context3 ]
MessageProxy = mms3.tracfone.com
Protocol = ip
Name = TracFone
Username =
IPv6.Settings = { }
Active = 0
Settings = { }
MessageCenter = http://mms-tf.net
Password =
Type = internet
AccessPointName = tfdata
[ /ril_0/context4 ]
Protocol = ip
Name = LaptopConnect (data cards)
Username =
IPv6.Settings = { }
Active = 1
Settings = { Address=10.242.218.1 Interface=rmnet_usb0
Gateway=10.242.218.2 Method=static Netmask=255.255.255.0
DomainNameServers=172.26.38.1,172.26.38.2, }
Password =
Type = internet
AccessPointName = Broadband
[ /ril_0/context5 ]
Protocol = ip
Name = Data Connect (old)
Username =
IPv6.Settings = { }
Active = 0
Settings = { }
Password =
Type = internet
AccessPointName = isp.cingular
[ /ril_0/context6 ]
Protocol = ip
Name = LTE
Username =
IPv6.Settings = { }
Active = 0
Settings = { }
Password =
Type = internet
AccessPointName = pta
[ /ril_0/context7 ]
Protocol = ip
Name = Internet
Username =
IPv6.Settings = { }
Active = 0
Settings = { }
Password =
Type = internet
AccessPointName = att.mvno
nuntium.log:
phablet@ubuntu-phablet:~$ cat .cache/upstart/nuntium.log
2014/05/28 09:25:49 Received ReceiveNotification() method call from 301000
2014/05/28 09:25:49 Push data
01 06 27 61 70 70 6c 69 63 61 74 69 6f 6e 2f 76 |..'application/v|
0010 6e 64 2e 77 61 70 2e 6d 6d 73 2d 6d 65 73 73 61 |nd.wap.mms-messa|
0020 67 65 00 af 84 8d 01 81 b4 84 8c 82 98 43 44 30 |ge...CD0|
0030 35 32 38 31 33 32 35 34 35 34 30 30 30 33 38 30 |5281325454000380|
0040 30 30 30 30 30 30 30 30 00 8d 90 89 18 80 2b 31 |..+1|
0050 36 31 37 36 39 39 30 36 35 35 2f 54 59 50 45 3d |6176990655/TYPE=|
0060 50 4c 4d 4e 00 96 02 ea 00 8a 80 8e 02 80 00 88 |PLMN|
0070 05 81 03 05 46 00 83 68 74 74 70 3a 2f 2f 31 36 |F..http://16|
0080 36 2e 32 31 36 2e 32 33 30 2e 35 3a 38 30 31 35 |6.216.230.5:8015|
0090 2f 30 35 32 38 31 33 32 35 34 35 34 30 30 30 33 |/052813254540003|
00a0 38 30 30 30 30 30 30 30 30 30 00 |80.|
Setting HeaderLength to 39
Setting ContentType to application/vnd.wap.mms-message
Setting ApplicationId to 4
Setting TransactionId to CD05281325454000380
Setting Version to 0x10 == 16
Setting From to +16176990655/TYPE=PLMN
Next string encoded with: utf-8
Setting Subject to
Setting Class to 0x80 == 128
Setting Size to 32768
Expiry token: 81
Message Expiry 197958, 0
Setting ContentLocation to http://166.216.230.5:8015/05281325454000380
2014/05/28 09:25:49 Context type: internet MessageCenter:
http://mmsc.mobile.att.net MessageProxy: proxy.mobile.att.net Active: false
2014/05/28 09:25:49 Context type: internet MessageCenter:
http://mmsc.cingular.com/
[Touch-packages] [Bug 1304754] Re: gccgo has issues when page size is not 4kB
** Attachment added: The dmesg output from stilson-06 (CI) machine. https://bugs.launchpad.net/ubuntu/+source/gccgo-4.9/+bug/1304754/+attachment/4160054/+files/stilson-06_dmesg_output.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9 in Ubuntu. https://bugs.launchpad.net/bugs/1304754 Title: gccgo has issues when page size is not 4kB Status in The GNU Compiler Collection: Fix Released Status in “gcc-4.9” package in Ubuntu: Fix Released Status in “gccgo-4.9” package in Ubuntu: Invalid Status in “gcc-4.9” source package in Trusty: Invalid Status in “gccgo-4.9” source package in Trusty: In Progress Status in “gcc-4.9” source package in Utopic: Fix Released Status in “gccgo-4.9” source package in Utopic: Invalid Bug description: On kernels 3.13-18 and 3.13-23 (there may be others) the kernel is killing gccgo compiled binaries [18519.444748] jujud[19277]: bad frame in setup_rt_frame: nip lr [18519.673632] init: juju-agent-ubuntu-local main process (19220) killed by SEGV signal [18519.673651] init: juju-agent-ubuntu-local main process ended, respawning In powerpc/kernel/signal_64.c: sys_rt_sigreturn is jumping to the badframe: label and executing an unconditional force_sigsegv which is delivered to the userland process. Like C++, gccgo tries to decode SIGSEGV as a nil pointer access and blame some random function that happened to be the top stack frame. Reverting to the 3.13-08 kernel appears to resolve the issue which (weakly) points the finger at the recent switch to 64k pages. To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1304754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304754] Re: gccgo has issues when page size is not 4kB
Is there any way to verify if a Debian package has been built with this gccgo fix? Procedure: I downloaded the 14.04 debian packages from: http://juju-ci.vapour.ws:8080/job/publish-revision/690/ These packages were built on stilson-07 which has the PPA and the fixed version of gccgo. Then I ran apt-get upgrade/update sudo dpkg -i *1.20.2* juju bootstrap -v -e local –debug juju deploy local:trusty/ubuntu juju ssh ubuntu/0 Segmentation fault on stilson-01: http://pastebin.ubuntu.com/7832678/ According to line 372 the dmesg output: http://paste.ubuntu.com/7832700/ This appears to be the same problem, the deb packages were not built with the fix. I am also able to reproduce this Segmentation fault on the CI machine stilson-06. http://pastebin.ubuntu.com/7836776/ The CI build machine has the toolchain-r PPA and the fixed level of gccgo: http://pastebin.ubuntu.com/7836812/ The dmesg output is attached. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9 in Ubuntu. https://bugs.launchpad.net/bugs/1304754 Title: gccgo has issues when page size is not 4kB Status in The GNU Compiler Collection: Fix Released Status in “gcc-4.9” package in Ubuntu: Fix Released Status in “gccgo-4.9” package in Ubuntu: Invalid Status in “gcc-4.9” source package in Trusty: Invalid Status in “gccgo-4.9” source package in Trusty: In Progress Status in “gcc-4.9” source package in Utopic: Fix Released Status in “gccgo-4.9” source package in Utopic: Invalid Bug description: On kernels 3.13-18 and 3.13-23 (there may be others) the kernel is killing gccgo compiled binaries [18519.444748] jujud[19277]: bad frame in setup_rt_frame: nip lr [18519.673632] init: juju-agent-ubuntu-local main process (19220) killed by SEGV signal [18519.673651] init: juju-agent-ubuntu-local main process ended, respawning In powerpc/kernel/signal_64.c: sys_rt_sigreturn is jumping to the badframe: label and executing an unconditional force_sigsegv which is delivered to the userland process. Like C++, gccgo tries to decode SIGSEGV as a nil pointer access and blame some random function that happened to be the top stack frame. Reverting to the 3.13-08 kernel appears to resolve the issue which (weakly) points the finger at the recent switch to 64k pages. To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1304754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346819] Re: Unity8 non-upstart tests fight for hardware with unity-system-compositor
** Tags added: qa-broken-test qa-daily-testing qa-landing-email -- 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/1346819 Title: Unity8 non-upstart tests fight for hardware with unity-system- compositor Status in “unity8” package in Ubuntu: In Progress Bug description: Running unity8 AP tests (specifically unity8.shell.tests.test_upstart.UpstartIntegrationTests.test_no_sigstop) sees the following and the testing gets aborted: 06:09:34.549 INFO _logging:41 - Starting test unity8.shell.tests.test_upstart.UpstartIntegrationTests.test_no_sigstop (Native Device) 06:09:34.553 WARNING testcase:112 - No tracing available - install the python-autopilot-trace package! 06:09:34.574 WARNING testcase:159 - Process manager backend unavailable, application snapshot support disabled. 06:09:34.595 WARNING utilities:266 - WARNING: in file /home/phablet/autopilot/unity8/shell/tests/__init__.py, line 148 in setUp This function is deprecated. Please use 'the Touch class to instantiate a device object' instead. 06:09:34.767 WARNING utilities:266 - WARNING: in file /home/phablet/autopilot/unity8/shell/tests/test_upstart.py, line 90 in test_no_sigstop This function is deprecated. Please use 'fixtures.EnvironmentVariable' instead. 06:09:34.777 WARNING utilities:266 - WARNING: in file /home/phablet/autopilot/unity8/shell/tests/test_upstart.py, line 59 in _launch_unity This function is deprecated. Please use 'fixtures.EnvironmentVariable' instead. WARNING: QApplication was not created in the main() thread. Testability driver loaded. Wire protocol version is 1.4. g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Terminated === The issue is occurring on both mako and flo. Steps to reproduce: 1. bzr branch lp:ububntu-test-cases/touch 2. cd touch 3. ./scripts/provision.sh -i touch -r 110 -n NETWORK_FILE -w (where network file is your wifi file ) 4. scripts/jenkins.sh -a unity8 -p /tmp/results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1346819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314781] Re: Translations for available apps not displayed
*** This bug is a duplicate of bug 1302622 *** https://bugs.launchpad.net/bugs/1302622 ** This bug has been marked a duplicate of bug 1302622 Queries and responses should be automatically localised -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1314781 Title: Translations for available apps not displayed Status in Click Package metadata search service: New Status in “unity-scope-click” package in Ubuntu: Fix Released Bug description: Currently, translations for available apps are not being displayed in the click scope. For the click scope side, we need to send the Accept- Language header in all HTTP requests, so that the server can know what language the data should be displayed in. For the server side, it needs to support filtering on Accept-Language, and to return results with the translated version of displayed data, rather than the default version. To manage notifications about this bug go to: https://bugs.launchpad.net/click-package-index/+bug/1314781/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
