[Touch-packages] [Bug 1369369] Re: → and ← characters overlap with the next character
*** This bug is a duplicate of bug 894288 *** https://bugs.launchpad.net/bugs/894288 ** This bug has been marked a duplicate of bug 894288 Mono: the characters ▶▼▷◢←↑↓→ are too big -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/1369369 Title: → and ← characters overlap with the next character Status in “ubuntu-font-family-sources” package in Ubuntu: New Bug description: When using Ubuntu Mono in gnome-terminal, → and ← characters overlap into the next character. This is somewhat fine if they are surrounded by spaces, but it's hard to read when someone does a→b with no spaces around the arrow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1369369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371859] [NEW] can't update loaders.cache: permission denied
Public bug reported: upgrading that fresh Utopic 64 bits installation, i'm seeing that error into the dialog box: Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:3098): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. The terminal output is: oem@u64:~$ gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission denied oem@u64:~$ sudo gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission denied ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgdk-pixbuf2.0-0 2.30.8-1 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 20 08:00:57 2014 SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1371859 Title: can't update loaders.cache: permission denied Status in “gdk-pixbuf” package in Ubuntu: New Bug description: upgrading that fresh Utopic 64 bits installation, i'm seeing that error into the dialog box: Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:3098): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. The terminal output is: oem@u64:~$ gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission denied oem@u64:~$ sudo gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission denied ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgdk-pixbuf2.0-0 2.30.8-1 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 20 08:00:57 2014 SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1371859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371766] Re: Latest CVE-2014-5270 patch breaks ElGamal keys of 16k
...and it works. So, the problem is: with the latest patch, the usual amount of secure memory (32768 bytes) is not sufficient anymore. I just raised it to another arbitrary number (262144) and it works fine. Wouldn't it be sufficient to just raise secmem_init() in g10/gpg.c ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1371766 Title: Latest CVE-2014-5270 patch breaks ElGamal keys of 16k Status in “gnupg” package in Ubuntu: Confirmed Status in “gnupg” package in Debian: New Bug description: I'm currenty using Ubuntu 12.04.5 LTS, 32-bit. This is what i get with GnuPG version 1.4.11-3ubuntu2.6 using Enigmail (correct behavior): 2014-09-19 13:44:09.630 [CONSOLE] enigmail /usr/bin/gpg --charset utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2 -a -t --encrypt --encrypt-to 0x135C7291 - r 0x0B7D1987135C7291 -u 0x135C7291 2014-09-19 13:44:40.545 [DEBUG] enigmailCommon.jsm: encryptMessageEnd: uiFlags=16, sendFlags=0142, outputLen=5768 2014-09-19 13:44:40.545 [DEBUG] enigmailCommon.jsm: parseErrorOutput: status message: gpg: 0x0B7D1987135C7291: skipped: public key already present [GNUPG:] BEGIN_ENCRYPTION 2 9 [GNUPG:] END_ENCRYPTION 2014-09-19 13:44:40.548 [DEBUG] enigmailCommon.jsm: parseErrorOutput: statusFlags = 8000 2014-09-19 13:44:40.549 [DEBUG] enigmailMsgComposeOverlay.js: Enigmail.msg.keySelection(): return toAddrStr=0x0B7D1987135C7291 bccAddrStr= 2014-09-19 13:44:40.550 [DEBUG] enigmailMsgComposeOverlay.js: hasAttachments = false 2014-09-19 13:44:40.551 [DEBUG] enigmailMsgComposeOverlay.js: Enigmail.msg.editorGetContentAs 2014-09-19 13:44:40.551 [DEBUG] enigmailMsgComposeOverlay.js: Enigmail.msg.replaceEditorText: 2014-09-19 13:44:40.556 [DEBUG] enigmailMsgComposeOverlay.js: Enigmail.msg.editorInsertText 2014-09-19 13:44:40.569 [DEBUG] enigmailMsgComposeOverlay.js: Enigmail.msg.editorInsertText 2014-09-19 13:44:40.573 [DEBUG] enigmailMsgComposeOverlay.js: Enigmail.msg.editorGetContentAs 2014-09-19 13:44:40.574 [DEBUG] enigmailMsgComposeOverlay.js: Enigmail.msg.editorGetCharset 2014-09-19 13:44:40.574 [DEBUG] enigmailMsgComposeOverlay.js: Enigmail.msg.encryptMsg: charset=utf-8 2014-09-19 13:44:40.575 [DEBUG] enigmail.js: Enigmail.encryptMessage: 9 bytes from 0x135C7291 to 0x0B7D1987135C7291 (67) 2014-09-19 13:44:40.575 [DEBUG] enigmailCommon.jsm: encryptMessageStart: uiFlags=1, from 0x135C7291 to 0x0B7D1987135C7291, hashAlgorithm=null (0043) 2014-09-19 13:44:40.575 [DEBUG] enigmailCommon.jsm: getEncryptCommand: hashAlgorithm=null 2014-09-19 13:44:40.577 enigmailCommon.jsm: execStart: command = /usr/bin/gpg --charset utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2 -a -t --encrypt --sign --encrypt-to 0x135C7291 -r 0x0B7D1987135C7291 -u 0x135C7291, needPassphrase=1, domWindow=[object ChromeWindow], listener=[object Object] 2014-09-19 13:44:40.577 [DEBUG] enigmailCommon.jsm: getPassphrase: 2014-09-19 13:44:40.578 [CONSOLE] enigmail /usr/bin/gpg --charset utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2 -a -t --encrypt --sign --encrypt-to 0x135C7291 -r 0x0B7D1987135C7291 -u 0x135C7291 --use-agent 2014-09-19 13:45:15.448 [DEBUG] enigmailCommon.jsm: encryptMessageEnd: uiFlags=1, sendFlags=0043, outputLen=5906 2014-09-19 13:45:15.448 [DEBUG] enigmailCommon.jsm: parseErrorOutput: status message: [GNUPG:] USERID_HINT 0B7D1987135C7291 Ciaby ci...@autistici.org [GNUPG:] NEED_PASSPHRASE 0B7D1987135C7291 0B7D1987135C7291 17 0 [GNUPG:] GOOD_PASSPHRASE gpg: 0x0B7D1987135C7291: skipped: public key already present [GNUPG:] BEGIN_SIGNING [GNUPG:] SIG_CREATED S 17 10 01 1411152280 D0178161A8FA6E506BD07C000B7D1987135C7291 [GNUPG:] BEGIN_ENCRYPTION 2 9 [GNUPG:] END_ENCRYPTION This is what i get with GnuPG version 1.4.11-3ubuntu2.7 using Enigmail (incorrect behavior): 2014-09-18 22:41:19.504 [CONSOLE] enigmail /usr/bin/gpg --charset utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2 -a -t --encrypt --sign --encrypt-to 0x135 C7291 -r 0x834AC0577A169C63 -u 0x135C7291 --use-agent 2014-09-18 22:41:37.732 [DEBUG] enigmailCommon.jsm: encryptMessageEnd: uiFlags=1, sendFlags=0043, outputLen=0 2014-09-18 22:41:37.733 [DEBUG] enigmailCommon.jsm: parseErrorOutput: status message: [GNUPG:] USERID_HINT 0B7D1987135C7291 Ciaby ci...@autistici.org [GNUPG:] NEED_PASSPHRASE 0B7D1987135C7291 0B7D1987135C7291 17 0 [GNUPG:] GOOD_PASSPHRASE gpg: out of secure memory while allocating 2048 bytes gpg: (this may be caused by too many secret keys used simultaneously or due to excessive large key sizes) Obviously, the latest security patch breaks ElGamal encryption with large keys (in this case, 16384 bytes). Although GnuPG doesn't allow to generate these keys, the PGP standard (and GnuPG itself) supports large key
[Touch-packages] [Bug 757551] Re: upowerd is using too much memory
I can corroborate the link to the logitech universal receiver, however for me upowerd eats so much memory that the whole system slows down. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/757551 Title: upowerd is using too much memory Status in “upower” package in Ubuntu: Confirmed Bug description: Binary package hint: upower I currently have 36 days of uptime on my laptop (using suspend a lot) and over time, I've noticed that the upowerd process got to the top of the list in terms of memory usage by claiming 1GB+. I can manage with this situation since I have 6GB of physical memory, but I'm sure that people with less in their laptops will not be so fortunate. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: upower 0.9.5-4 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic x86_64 Architecture: amd64 Date: Mon Apr 11 09:47:23 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/upower/upowerd InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcEnviron: SourcePackage: upower To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/757551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368788] Re: Ubuntu One TC string/link not in pot file
** Also affects: ubuntu-translations Importance: Undecided Status: New ** Changed in: ubuntu-translations Status: New = Triaged ** Changed in: ubuntu-translations Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1368788 Title: Ubuntu One TC string/link not in pot file Status in Ubuntu Translations: Triaged Status in “ubuntuone-credentials” package in Ubuntu: New Bug description: This string has not been catched by the xgettext 'I agree to the a href=https://one.ubuntu.com/terms/;span style= color: #dd4814;Ubuntu One Tamp;Cs/span/a' So currently is not translated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1368788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368593] Re: no funciona flash player
No, no deberías esperar que la gente te responda en español en la sección «Bugs» del sitio de desarrollo de Ubuntu. Para realizar preguntas como esa, dirígete a la sección «Answers». ** Changed in: xorg (Ubuntu) Status: New = Invalid -- 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/1368593 Title: no funciona flash player Status in “xorg” package in Ubuntu: Invalid Bug description: no funciona flahs players desde que tengo Ubuntu 14 por favor respondame en español ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Sep 12 09:39:00 2014 DistUpgraded: 2014-04-19 10:33:48,184 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:2400] InstallationDate: Installed on 2013-04-24 (506 days ago) InstallationMedia: LINUX 12.10 - Release i386 MachineType: CLEVO CO. W24xCZ ProcEnviron: LANGUAGE=es PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=696f463a-f386-4dc8-b6d9-7d298907db0d ro splash quiet SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-19 (145 days ago) dmi.bios.date: 12/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W24xCZ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/18/2012:svnCLEVOCO.:pnW24xCZ:pvrNotApplicable:rvnCLEVOCO.:rnW24xCZ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W24xCZ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 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.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Sep 12 08:34:13 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8684 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1368593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353560] Re: Don't black screen when on call with speakerphone
** Branch linked: lp:~andreas-pokorny/powerd/blank-on-proximity- powerstate ** Branch linked: lp:~andreas-pokorny/telepathy-ofono/control-proximity- handling-in-powerd -- 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/1353560 Title: Don't black screen when on call with speakerphone Status in Dialer app for Ubuntu Touch: Invalid Status in PowerD: In Progress Status in Telepathy Ofono: In Progress Status in Unity System Compositor: Invalid Status in “unity-system-compositor” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Invalid Bug description: mako #175 The proximity sensor (screen turns off when something get close to the phone) should be turned off when loud speaker is on otherwise it's very difficult to interact with the phone and the dialer, or to unlock the phone if the call is long. (it might also depends on where the sensor is on the hardware) TEST CASE: 1. Open the dialer and place a call 2. Switch on the loud speaker and put your phone flat on the table. 3. Get your hand close to the sensor ACTUAL RESULT The screen turns off and user cannot interact with the dialer app EXPECTED RESULT Screen stays on. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1353560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354560] Re: Indicator doesn't show connected status when associated with hidden network
** Branch unlinked: lp:~andreas-pokorny/powerd/blank-on-proximity- powerstate ** Branch unlinked: lp:~andreas-pokorny/telepathy-ofono/control- proximity-handling-in-powerd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1354560 Title: Indicator doesn't show connected status when associated with hidden network Status in “indicator-network” package in Ubuntu: New Bug description: After connecting to a hidden wifi network the indicator does not correctly show the connection status. Instead of the connected icon in the top bar there's just a blank space, the hidden network shows up in the indicator's network list twice, and there's no check mark next to either of the entries in the network list. The phone is associated with the wireless network however and has a functioning network connection. I'm attaching screenshots of the indicator when this is happening as well as other data requested in bug #1202806. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1247216] Re: Support for XMPP
Just to add some context on the status quo: What's working: - Telepathy framework, just make sure you have telepathy-gabble installed for XMPP support - You can manually add an account using mc-tool - You can use mc-tool to set the account online/offline - You can receive messages, BUT you only see them in notification and the message overview What's missing/not working: - Messaging app needs work to understand more than text messages coming through telepathy from oFono - You can't reply to messages. Seems there is some logic that breaks that as it was written only with SMS based text messaging in mind. - Accounts plugin needs to be created to have a UI for managing the XMPP account(s) JFTR: This actually applies also to all(?) other telepathy (and by extension through haze also libpurple) messaging protocols like SIPe(MS Lync/OCS), ICQ, GaduGadu, SIP/SIMPLE, … -- 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/1247216 Title: Support for XMPP Status in “messaging-app” package in Ubuntu: In Progress Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Confirmed Bug description: Hi All, basically there are three things that block me to move to Ubuntu Touch. A missing spotify app (already in developement :) ), a missing mail app (planned for 14.04 :) ) and finally a missing IM app -- especially for XMPP. Thusly, I propose adding support for XMPP to the messaging-app. It already uses telepathy so we should be able to add this functionality. I would also be willing to work on this if somebody points me out where to start. I guess we would have to break this down into several work packages: setting up accounts, online/offline handling of friends, choosing protocols when composing a message etc. But first I would like to get some feedback if you would be okay with such a feature. Maybe it is already planned? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1247216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367341] Re: proximity sensor blanks screen when dialer is not active app
The proposed solution will deactivate proximity sensor when a different than the default output is used for a call. So the screen will stay on, when someone interacts with the phone... -- 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/1367341 Title: proximity sensor blanks screen when dialer is not active app Status in PowerD: In Progress Status in “dialer-app” package in Ubuntu: New Status in “unity-system-compositor” package in Ubuntu: New Bug description: Steps: 1. Make a phone call with BT so that you are not holding the phone to hear and talk 2. Push the power button to blank the screen 3. Push the power button again, observe that you are at the welcome screen 4. Wave a finger over the proximity sensor Effect: The screen blanks while finger is over the sensor Expected: The sensor only blanks the screen while the dialer app is being used this is kirllin r23 To manage notifications about this bug go to: https://bugs.launchpad.net/powerd/+bug/1367341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315905] Re: [Alienware 14, Realtek ALC668, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1315905 Title: [Alienware 14, Realtek ALC668, Speaker, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Speakers do not work at all. Tried the instructions from here (and various other places)without luck. I reverted the alsa-base.conf and rebooted before filing this bug. http://askubuntu.com/questions/390835/sound-from-headphones-but-not- from-speakers-in-alienware-14 $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dane 2115 F pulseaudio /dev/snd/controlC0: dane 2115 F pulseaudio CurrentDesktop: GNOME CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun May 4 11:24:34 2014 InstallationDate: Installed on 2014-04-18 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dane 2115 F pulseaudio /dev/snd/controlC0: dane 2115 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Alienware 14, Realtek ALC668, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2014 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: 07MJ2Y dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd02/25/2014:svnAlienware:pnAlienware14:pvrA08:rvnAlienware:rn07MJ2Y:rvrA00:cvnAlienware:ct8:cvrA08: dmi.product.name: Alienware 14 dmi.product.version: A08 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-05-04T11:23:10.256695 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1315905/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301623] Re: unity freezes when moving windows among workspaces
Same issues, 2 solutions are to either switch between workspace with ctrl+alt+(arrow keys) until compiz crashes and returns to normal state(which makes me think that is a bug related to compiz) or ctrl+alt+f1 and reboot from terminal. -- 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/1301623 Title: unity freezes when moving windows among workspaces Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: Sometimes In Ubuntu 14.04, when I move windows from one workspace to another, Unity freezes, letting me with this 4 workspaces overview. I have to use terminal and restart Unity to resolve it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 23:26:06 2014 DistUpgraded: 2014-03-18 07:46:56,695 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:365e] InstallationDate: Installed on 2014-02-10 (51 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) MachineType: LENOVO 10104 ProcEnviron: LANGUAGE=cs PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=3a918684-e656-4e86-9b7b-22e0fd6b2135 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-18 (15 days ago) dmi.bios.date: 03/21/2013 dmi.bios.vendor: LENOVO dmi.bios.version: ELKT31AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: 3193 STD dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.name: 10104 dmi.product.version: Lenovo C440 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Mar 31 16:48:50 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8192 vendor LEN xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1301623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371642] Re: ADB over WIFI
I've reopened the issue as this command obviously does not work with my Nexus 4 running Ubuntu Touch. I should have made it more clear that I'm talking about UT though. ** Changed in: android-tools (Ubuntu) Status: Invalid = New ** Changed in: ubuntu-system-settings (Ubuntu) Status: Invalid = New ** Summary changed: - ADB over WIFI + ADB over WIFI with Ubuntu Touch ** Description changed: - There's currently no option to connect to ADB over WIFI. Some Android - ROMs like Cyanogenmod support this feature and it comes in quite handy. + There is currently no option to connect to an Ubuntu Touch device using + ADB over WIFI. Some Android ROMs like Cyanogenmod support this feature + and it comes in quite handy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1371642 Title: ADB over WIFI with Ubuntu Touch Status in “android-tools” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: New Bug description: There is currently no option to connect to an Ubuntu Touch device using ADB over WIFI. Some Android ROMs like Cyanogenmod support this feature and it comes in quite handy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1371642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'
** Tags added: utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/619003 Title: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib /gdk-pixbuf-2.0/2.10.0/loaders.cache' Status in “gdk-pixbuf” package in Ubuntu: Confirmed Status in “gdk-pixbuf” package in Debian: New Bug description: During installation of updated version of libgdk-pixbuf2.0-0 on August 10th 2010, the apt term.log contained multiple (300) copies of the following warning: (gtk-update-icon-cache:4729): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory Nevertheless, the file complained about exists, and is readable in gedit. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgdk-pixbuf2.0-0 2.21.6-2ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1 Uname: Linux 2.6.35-15-generic x86_64 Architecture: amd64 CheckboxSubmission: 363004b1d940f0fc558ab8c98655a145 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 Date: Mon Aug 16 18:13:29 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta amd64 (20100318) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdk-pixbuf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352253] Re: hotkey to toggle microphone mute (ALT + F4) shows a speaker, not a microphone
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-sound (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1352253 Title: hotkey to toggle microphone mute (ALT + F4) shows a speaker, not a microphone Status in “indicator-sound” package in Ubuntu: Confirmed Bug description: This is incorrect for 2 reasons: 1) The overlay should show a microphone icon since that is what is being toggled. 2) It's currently using the same icon as the speaker / sound output mute hotkey (ALT + F1). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute': (true, '', [false]), 'phone-settings': (true, '', []), 'mic-volume': (true, '', [0.510009765625]), 'scroll': (true, 'i', []), 'vlc.desktop': (true, '', [{'running': false, 'state': 'Paused'}]), 'previous.vlc.desktop': (true, '', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '', [{'running': false, 'state': 'Paused'}]), 'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i', [0.350067138671875]), 'play-playlist.vlc.desktop': (true, 's', []), 'root': (true, '', [{'title': 'Son', 'accessible-desc': 'Volume (35%)', 'icon': ('themed', ['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume', 'audio']), 'visible': true}]), 'play.rhythmbox.desktop': (true, '', ['Paused']), 'play-playlist.rhythmbox.desktop': (true, 's', []), 'next.rhythmbox.desktop': (true, '', []), 'play.vlc.desktop': (true, '', ['Paused'])},) ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 4 10:39:43 2014 InstallationDate: Installed on 2014-04-11 (114 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409) SourcePackage: indicator-sound UpgradeStatus: Upgraded to utopic on 2014-05-08 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1352253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 869704] Re: oneconf-service crashed with SystemError in open(): E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_multiverse_i18n_Translation-en
*** This bug is a duplicate of bug 1051935 *** https://bugs.launchpad.net/bugs/1051935 i dont see the task bar on the left side and on the top of the screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/869704 Title: oneconf-service crashed with SystemError in open(): E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_multiverse_i18n_Translation-en - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_main_i18n_Translation-en - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_multiverse_binary-i386_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_universe_binary-i386_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_restricted_binary-i386_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_main_binary-i386_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_multiverse_binary-amd64_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_universe_binary-amd64_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_restricted_binary-amd64_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_oneiric_main_binary-amd64_Packages - open (24: Too many open files) Status in “python-apt” package in Ubuntu: Confirmed Bug description: none i know of ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: oneconf 0.2.6.7 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Fri Oct 7 00:14:43 2011 ExecutablePath: /usr/share/oneconf/oneconf-service InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110922) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/oneconf/oneconf-service ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 PythonArgs: ['/usr/share/oneconf/oneconf-service'] SourcePackage: oneconf Title: oneconf-service crashed with SystemError in open(): E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_multiverse_i18n_Translation-en - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_main_i18n_Translation-en - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_multiverse_binary-i386_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_universe_binary-i386_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_restricted_binary-i386_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_main_binary-i386_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_multiverse_binary-amd64_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_universe_binary-amd64_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_restricted_binary-amd64_Packages - open (24: Too many open files), E:Could not open file /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_oneiric_main_binary-amd64_Packages - open (24: Too many open files) UpgradeStatus: Upgraded to oneiric on 2011-10-05 (2 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev powerdev sambashare scanner tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/869704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334495] Re: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts
** Branch linked: lp:debian/fonts-android -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Bug description: [Info for the Trusty SRU request] Please see the description at bug #1351092. [Original description] Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a italic font, others in a normal font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the normal characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of locale looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= fc-match: »DejaVuSans.ttf: DejaVu Sans Book« This is my first bug filed at launchpad. I filed it for language- selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1334495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
** Branch linked: lp:debian/fonts-android -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Status in “fonts-android” package in Debian: New Bug description: [Impact] fontconfig configuration settings, aimed at making the Droid Sans Fallback font be used to render Chinese, fails sometimes in an unpredictable way. This seems to be caused by the file 65-droid-sans- fonts.conf, which is currently installed by fonts-droid. Consequently that file is proposed to be dropped from fonts-droid. Some fontconfig files in language-selector are proposed to be changed accordingly. Example problems: * One of the AR PL UMing fonts is sometimes used instead of Droid Sans Fallback in case of a Chinese locale. * Buggy rendering of Chinese contents in qt apps in case of a non-Chinese locale (bug #1334495). * Droid Sans Fallback can't be used in Ubuntu Touch (see discussion at bug #1346766). [Test Case] Since the behaviour is not always buggy, it's hard to present a proper test case. Instead I have to refer to the discussions in this bug report as well as the above mentioned bugs. [Regression Potential] While the fonts-droid package installs a bunch of fonts for various languages, only the Droid Sans Fallback font is used as part of Ubuntu's default font configuration. The regression risk for Chinese users is reasonably very low. There is a risk, though, that this change leads to surprise changes for individual users who make use of other fonts but Droid Sans Fallback. There is no indication that those other fonts are widely used. [Original description] There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: Droid Sans Fallback Regular uming.ttc: AR PL UMing CN Light uming.ttc: AR PL UMing HK Light ukai.ttc: AR PL UKai CN Book DejaVuSans.ttf: DejaVu Sans Book Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368647] Re: GPS and location detection not working on Nexus 4
I have switched to rtm r1 single-boot and got location working in OSMTouch, Google maps and a weather site on the web. The accuracy indicated that the GPS was involved. But after a reboot, the location no longer works for me. Will see if it gets going again if I wait. It sure feels strange though, that it should suddenly stop working after a reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1368647 Title: GPS and location detection not working on Nexus 4 Status in “location-service” package in Ubuntu: Confirmed Bug description: Mako with MultiROM, utopic r239 None of the apps I have tried including Weather, Google maps, OSM Touch and SensorStatus are able to use the phone's GPS. The SensorStatus app actually reports Found supported backend, but finds no position or other GPS data. Location detection on the other hand is doing something, but it is really far off when it comes to determining the actual location of the device. The Weather app suggests my location as Vänsjö, Jämtland, which is about 400 km north of Stockholm where I am at. OSM Touch reports no location available and Google maps Your location could not be determined I don't know if the GPS has to waken up somehow, but it has not shown any form of life for me on Ubuntu Touch, even though it works perfectly fine when booting the phone as Android. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1368647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
I also ran into this issue after upgrading to Trusty (nvidia driver 331.38). Checking Force full screen redraws and Force synchronization between X and GLX seems to have helped. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared Status in “xorg” package in Ubuntu: Confirmed Bug description: As requested in Bug #1310633 I'm opening a new bug. With a previous version of Ubuntu I already had this flickering. With additional options for the kernel module I was able to fix the flickering. options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0 With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the flickering reappeared although the line is still present in options.conf. Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331. Changing the module name in options.conf to nvidia_331 X doesn't start anymore. Removing the NVreg_ModifyDeviceFiles option X is starting again, but does not solve the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Tue Apr 29 21:09:41 2014 DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2012-11-17 (528 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8540w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.24 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8540w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 29 21:06:04 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371899] [NEW] clang++ -flto fails to work unless -B /usr/lib/gold-ld is given
Public bug reported: clang++ -flto does not seem to configure everything properly: $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra /tmp/try-1083b9.o: file not recognized: Dateiformat nicht erkannt clang: error: linker command failed with exit code 1 (use -v to see invocation) $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra -B/usr/lib/gold-ld however, works properly. See the attached files for output from the same commands with -v added on the respective command lines. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: clang-3.4 1:3.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 20 12:53:53 2014 SourcePackage: llvm-toolchain-3.4 UpgradeStatus: Upgraded to trusty on 2014-08-29 (21 days ago) ** Affects: llvm-toolchain-3.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: Output of clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra -v 21 | tee clang-without-B.txt https://bugs.launchpad.net/bugs/1371899/+attachment/4209576/+files/clang-without-B.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1371899 Title: clang++ -flto fails to work unless -B /usr/lib/gold-ld is given Status in “llvm-toolchain-3.4” package in Ubuntu: New Bug description: clang++ -flto does not seem to configure everything properly: $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra /tmp/try-1083b9.o: file not recognized: Dateiformat nicht erkannt clang: error: linker command failed with exit code 1 (use -v to see invocation) $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra -B/usr/lib/gold-ld however, works properly. See the attached files for output from the same commands with -v added on the respective command lines. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: clang-3.4 1:3.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 20 12:53:53 2014 SourcePackage: llvm-toolchain-3.4 UpgradeStatus: Upgraded to trusty on 2014-08-29 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1371899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371899] Re: clang++ -flto fails to work unless -B /usr/lib/gold-ld is given
** Attachment added: output of lang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra -v -B/usr/lib/gold-ld 21 | tee clang-with-B.txt https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1371899/+attachment/4209579/+files/clang-with-B.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1371899 Title: clang++ -flto fails to work unless -B /usr/lib/gold-ld is given Status in “llvm-toolchain-3.4” package in Ubuntu: New Bug description: clang++ -flto does not seem to configure everything properly: $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra /tmp/try-1083b9.o: file not recognized: Dateiformat nicht erkannt clang: error: linker command failed with exit code 1 (use -v to see invocation) $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra -B/usr/lib/gold-ld however, works properly. See the attached files for output from the same commands with -v added on the respective command lines. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: clang-3.4 1:3.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 20 12:53:53 2014 SourcePackage: llvm-toolchain-3.4 UpgradeStatus: Upgraded to trusty on 2014-08-29 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1371899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
Actually, scratch that, the two options did not help at all. The flickering is terrible as before. I restarted the machine to make sure. When I have two Chrome browser windows open, one works fine, but the other flickers like crazy when switching tabs. I am using xmonad as my window manager, that might be contributing to the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared Status in “xorg” package in Ubuntu: Confirmed Bug description: As requested in Bug #1310633 I'm opening a new bug. With a previous version of Ubuntu I already had this flickering. With additional options for the kernel module I was able to fix the flickering. options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0 With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the flickering reappeared although the line is still present in options.conf. Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331. Changing the module name in options.conf to nvidia_331 X doesn't start anymore. Removing the NVreg_ModifyDeviceFiles option X is starting again, but does not solve the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Tue Apr 29 21:09:41 2014 DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2012-11-17 (528 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8540w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.24 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8540w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 29 21:06:04 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1371899] Re: clang++ -flto fails to work unless -B /usr/lib/gold-ld is given
The only difference that -B makes is running /usr/lib/gold-ld/ld instead of /usr/bin/ld -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1371899 Title: clang++ -flto fails to work unless -B /usr/lib/gold-ld is given Status in “llvm-toolchain-3.4” package in Ubuntu: New Bug description: clang++ -flto does not seem to configure everything properly: $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra /tmp/try-1083b9.o: file not recognized: Dateiformat nicht erkannt clang: error: linker command failed with exit code 1 (use -v to see invocation) $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra -B/usr/lib/gold-ld however, works properly. See the attached files for output from the same commands with -v added on the respective command lines. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: clang-3.4 1:3.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 20 12:53:53 2014 SourcePackage: llvm-toolchain-3.4 UpgradeStatus: Upgraded to trusty on 2014-08-29 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1371899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371899] Re: clang++ -flto fails to work unless -B /usr/lib/gold-ld is given
More importantly, -fuse-ld=gold per apt-get changelog binutils, here, does NOT work: binutils (2.23.52.20130722-1) unstable; urgency=low * New upstream snapshot. - Fix PR ld/15762, glibc being built without warning sections. * Set the libdir for arm64 to lib, not lib64. * Stop building the binutils-gold package, let binutils provide binutils-gold. Packages requiring gold should explicity pass -fuse-ld=gold to the compiler, packages requiring the bfd linker should pass -fuse-ld=bfd to the compiler. * Refresh patches. -- Matthias Klose d...@debian.org Mon, 22 Jul 2013 21:13:32 +0200 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1371899 Title: clang++ -flto fails to work unless -B /usr/lib/gold-ld is given Status in “llvm-toolchain-3.4” package in Ubuntu: New Bug description: clang++ -flto does not seem to configure everything properly: $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra /tmp/try-1083b9.o: file not recognized: Dateiformat nicht erkannt clang: error: linker command failed with exit code 1 (use -v to see invocation) $ clang++ -stdlib=libc++ try.cpp -O3 -flto -Wall -Wextra -B/usr/lib/gold-ld however, works properly. See the attached files for output from the same commands with -v added on the respective command lines. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: clang-3.4 1:3.4-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 20 12:53:53 2014 SourcePackage: llvm-toolchain-3.4 UpgradeStatus: Upgraded to trusty on 2014-08-29 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1371899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371853] Re: Logitech wireless mouse periodically loses correct click behaviour
Sam Brightman, thank you for reporting this and helping make Ubuntu better. As per http://www.gigabyte.com/products/product-page.aspx?pid=3010#bios an update to your BIOS is available (F8). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Once the BIOS is updated, then please mark this report Status New. Thank you for your understanding. ** Tags added: bios-outdated-f8 ** Tags added: regression-release ** Description changed: This problem began with the 14.04 upgrade. The mouse has always worked normally until then. - Approximately every 10 minutes - and possibly triggered by Alt-Tab - window switches/opening new windows - the mouse behaviour becomes rather - strange. Primarly, left-clicks are not registered properly to the - topmost window. They usually appear to go through to the window below - and it's not possible to switch focus to a new window (or any other - window). Mouse movement is unaffected and clicking on the original - window (which has grabbed the focus) seems to work. The Unity bar pops - out but is not clickable and rapidly re-hides. Sometimes individual - window elements are not usable even if the main window itself is. - Examples: - + Approximately every 10 minutes left-clicks are not registered properly to the topmost window. They usually appear to go through to the window below and it's not possible to switch focus to a new window (or any other window). Mouse movement is unaffected and clicking on the original window (which has grabbed the focus) seems to work. The Unity bar pops out but is not clickable and rapidly re-hides. Sometimes individual window elements are not usable even if the main window itself is. Examples: * In Thunderbird, left-pane account/folder selection works, but does not perform the corresponding update to the message list/preview panes when the folder selection changes. * dialogues are popped up where parts of the dialogue respond to clicks but other parts do not. Commonly, the dialogue title/menu bar is not responsive (it cannot be moved/closed). Sometimes right-clicking will restore focus to the appropriate window/area. Sometimes not. Unloading and reloading usbhid and hid_logitech modules does not help. - Restarting will fix the problem temporarily. I've found that switching - to a console and back will fix the problem temporarily too (Ctrl-Alt-F1, - Ctrl-Alt-F7). + Restarting will fix the problem temporarily. - Several very similar bugs exist for wireless headsets, mice and quite - often Logitech (although of course this is just a common brand) from - before 14.04, but for me this was never a problem previously. They are - being closed as expired even though they still exist in 14.04. Bug - #993655, Bug #1006156 and Bug #1337586 are examples. It is not 100% - clear to me if this is an xorg bug, but this is what was being suggested - in those tickets. The combination of module reloading not working with - console switching working (reinstall handlers?) does suggest X is - involved. + WORKAROUND: Switch to a console and back will fix the problem + temporarily via Ctrl-Alt-F1 and then Ctrl-Alt-F7. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 20 06:51:25 2014 DistUpgraded: 2014-06-16 02:07:17,816 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) -Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 4850 512MB GDDR3 [174b:e810] + Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller]) + Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 4850 512MB GDDR3 [174b:e810] MachineType: Gigabyte Technology Co.,
[Touch-packages] [Bug 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT
** Changed in: ibus (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1235567 Title: ibus-ui-gtk3 crashed with SIGABRT Status in IBus: Unknown Status in “ibus” package in Ubuntu: Triaged Bug description: Restarted system after installing updates was greeting me with that message ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sat Oct 5 08:17:10 2013 Disassembly: = 0x7f62f38f4f77: Cannot access memory at address 0x7f62f38f4f77 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2013-06-12 (114 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1235567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369512] Re: please move click sound out of qtubuntu-camera
This bug was fixed in the package apparmor-easyprof-ubuntu - 1.2.24 --- apparmor-easyprof-ubuntu (1.2.24) utopic; urgency=medium * ubuntu/camera: allow DBus communications with media-hub (LP: #1369512) * ubuntu/*: drop redundnat 'ptrace (read) peer=@{profile_name}' since we include it in the base abstraction now -- Jamie Strandboge ja...@ubuntu.com Tue, 16 Sep 2014 08:48:37 -0500 ** Changed in: apparmor-easyprof-ubuntu (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1369512 Title: please move click sound out of qtubuntu-camera Status in Media Hub: Invalid Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “qtubuntu-camera” package in Ubuntu: Triaged Bug description: RTM image 39 on mako media-hub 1.0.0+14.10.20140908~rtm-0ubuntu1 The Ubuntu Store have three torch apps, I installed all but none of them starts. The upstart log shows something bad re: apparmor/media- hub To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1369512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371916] [NEW] Downloading files fails for build libdvdcss2
Public bug reported: the name of the file has changed on VLC server. Line 95 has to be changed from: wget ${site}libdvdcss_${uversion}.orig.tar.gz to: wget ${site}libdvdcss_${uversion}.orig.tar.bz2 ** Affects: libdvdread (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdvdread in Ubuntu. https://bugs.launchpad.net/bugs/1371916 Title: Downloading files fails for build libdvdcss2 Status in “libdvdread” package in Ubuntu: New Bug description: the name of the file has changed on VLC server. Line 95 has to be changed from: wget ${site}libdvdcss_${uversion}.orig.tar.gz to: wget ${site}libdvdcss_${uversion}.orig.tar.bz2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvdread/+bug/1371916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371919] [NEW] kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD
Public bug reported: I have a gigabyte f2a88xn motherboard with built-in audio. In pavucontrol, under Configuration - Built-in audio (the first), there is Digital Stereo (HDMI) Output. When I disable it, the kern.log continuously reports HDMI ATI/AMD: no speaker allocation for ELD. This happens almost every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2824 F pulseaudio /dev/snd/controlC0: saverio2824 F pulseaudio CurrentDesktop: XFCE Date: Sat Sep 20 15:08:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (14 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1371919 Title: kern.log flooded with HDMI ATI/AMD: no speaker allocation for ELD Status in “alsa-driver” package in Ubuntu: New Bug description: I have a gigabyte f2a88xn motherboard with built-in audio. In pavucontrol, under Configuration - Built-in audio (the first), there is Digital Stereo (HDMI) Output. When I disable it, the kern.log continuously reports HDMI ATI/AMD: no speaker allocation for ELD. This happens almost every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2824 F pulseaudio /dev/snd/controlC0: saverio2824 F pulseaudio CurrentDesktop: XFCE Date: Sat Sep 20 15:08:50 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (14 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371920] [NEW] Bluetooth headphones don't show as output device in pavucontrol
Public bug reported: I have a Sennheiser MM450-X which are connected to the audio sink (Bluetooth Devices - Connect to audio sink) correctly, but they don't show in the pavucontrol output devices, so I can't use them. I can reproduce this bug every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio-module-bluetooth 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2824 F pulseaudio /dev/snd/pcmC1D0p: saverio2824 F...m pulseaudio /dev/snd/controlC0: saverio2824 F pulseaudio /dev/snd/pcmC0D3p: saverio2824 F...m pulseaudio CurrentDesktop: XFCE Date: Sat Sep 20 15:15:09 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (14 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2014-09-09T23:57:54.620518 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1371920 Title: Bluetooth headphones don't show as output device in pavucontrol Status in “pulseaudio” package in Ubuntu: New Bug description: I have a Sennheiser MM450-X which are connected to the audio sink (Bluetooth Devices - Connect to audio sink) correctly, but they don't show in the pavucontrol output devices, so I can't use them. I can reproduce this bug every time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio-module-bluetooth 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio2824 F pulseaudio /dev/snd/pcmC1D0p: saverio2824 F...m pulseaudio /dev/snd/controlC0: saverio2824 F pulseaudio /dev/snd/pcmC0D3p: saverio2824 F...m pulseaudio CurrentDesktop: XFCE Date: Sat Sep 20 15:15:09 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-05 (14 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd09/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2014-09-09T23:57:54.620518 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1371920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361911] Re: I have recently rebooted after the latest software update and suddenly my laptop is running slower than slow. top shows compliz is taking between 20% to more often 1
Tasks: 160 total, 1 running, 159 sleeping, 0 stopped, 0 zombie %Cpu(s): 63.2 us, 10.1 sy, 0.5 ni, 24.6 id, 1.4 wa, 0.0 hi, 0.4 si, 0.0 st KiB Mem: 2053488 total, 1163696 used, 889792 free,42084 buffers KiB Swap: 2084860 total,0 used, 2084860 free. 593244 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2159 doug 20 0 424732 169440 35288 S 145.3 8.3 8:36.72 compiz 1133 root 20 0 199332 69408 61120 S 23.2 3.4 1:15.23 Xorg 2575 doug 20 05428 1312988 R 11.6 0.1 0:00.03 top 2443 doug 20 0 560384 135440 41464 S 5.8 6.6 1:01.32 firefox compiz is choking my system to death... -- 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/1361911 Title: I have recently rebooted after the latest software update and suddenly my laptop is running slower than slow. top shows compliz is taking between 20% to more often 130% or more of the CPU (dual CPU). My system was running really well now it is very very slow. Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I have recently rebooted after the latest software update and suddenly my laptop is running slower than slow. 'Top 'shows compliz is taking between 20% to more often 130% or more of the CPU (dual CPU). My system was running really well now it is very very slow. doug@doug-AOD255E:~$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 doug@doug-AOD255E:~$ apt-cache policy compiz compiz: Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1 Candidate: 1:0.9.11.2+14.04.20140714-0ubuntu1 Version table: *** 1:0.9.11.2+14.04.20140714-0ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:0.9.11+14.04.20140409-0ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages doug@doug-AOD255E:~$ apt-cache policy unity unity: Installed: 7.2.2+14.04.20140714-0ubuntu1.1 Candidate: 7.2.2+14.04.20140714-0ubuntu1.1 Version table: *** 7.2.2+14.04.20140714-0ubuntu1.1 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140416-0ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages doug@doug-AOD255E:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Aug 27 09:21:53 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0349] Subsystem: Acer Incorporated [ALI] Device [1025:0349] InstallationDate: Installed on 2014-08-16 (10 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) MachineType: Acer AOD255E ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=e6ef8dfb-6153-419b-ba33-d5d31364e19c ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2011 dmi.bios.vendor: Acer dmi.bios.version: V3.15(DDR3) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE02_PT_E dmi.board.vendor: Acer dmi.board.version: V3.15(DDR3) dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V3.15(DDR3) dmi.modalias: dmi:bvnAcer:bvrV3.15(DDR3):bd02/15/2011:svnAcer:pnAOD255E:pvrV3.15(DDR3):rvnAcer:rnJE02_PT_E:rvrV3.15(DDR3):cvnAcer:ct10:cvrV3.15(DDR3): dmi.product.name: AOD255E dmi.product.version: V3.15(DDR3) dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 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
[Touch-packages] [Bug 1371758] Re: tzdata need update
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1371758 Title: tzdata need update Status in “tzdata” package in Ubuntu: New Bug description: Description: Ubuntu 14.04.1 LTS Release: 14.04 According to Russian goverment there was a lot of changes in tzdata v2014f. It would be nice if this version (or 2014g) will appear in Ubuntu in short amount of time. Announcement: http://mm.icann.org/pipermail/tz- announce/2014-August/23.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1371758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume
I am on Ubuntu 14.04 and am still experiencing this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: times out too early, stuck in PrepareForSleep, causing network and other services to not resume Status in “systemd” package in Ubuntu: Invalid Status in “systemd-shim” package in Ubuntu: Fix Released Status in “systemd” source package in Saucy: Invalid Status in “systemd-shim” source package in Saucy: Fix Released Status in “systemd” source package in Trusty: Invalid Status in “systemd-shim” source package in Trusty: Fix Released Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. SRU INFORMATION: Reproducer: - Force suspend to take very long by adding a sleep: echo -e '#!/bin/sh\nsleep 15\nexit 1' | sudo tee /usr/lib/pm-utils/sleep.d/00break (this will also make suspend fail, which eases testing) - Suspend from the menu or with sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Suspend true - With the 13.10 final version, systemd-shim will (often) time out, and the next Suspend call from above will fail with Operation already in progress and the network does not come back up. With the fixed version, network should be back up and the Suspend() call can be issued many times. Fix: https://github.com/desrt/systemd-shim/commit/136ed1143077d13c2 https://github.com/desrt/systemd-shim/commit/16a7fdc0652ad78f4 Regression potential: Errors in this code could potentially break suspend/shutdown completely, so for verification both of these functionalities ought to be tested on real hardware. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume
Chris Morris, if you are experiencing an issue still, then this bug report had nothing to do with your problem. Please file a new report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: times out too early, stuck in PrepareForSleep, causing network and other services to not resume Status in “systemd” package in Ubuntu: Invalid Status in “systemd-shim” package in Ubuntu: Fix Released Status in “systemd” source package in Saucy: Invalid Status in “systemd-shim” source package in Saucy: Fix Released Status in “systemd” source package in Trusty: Invalid Status in “systemd-shim” source package in Trusty: Fix Released Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. SRU INFORMATION: Reproducer: - Force suspend to take very long by adding a sleep: echo -e '#!/bin/sh\nsleep 15\nexit 1' | sudo tee /usr/lib/pm-utils/sleep.d/00break (this will also make suspend fail, which eases testing) - Suspend from the menu or with sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Suspend true - With the 13.10 final version, systemd-shim will (often) time out, and the next Suspend call from above will fail with Operation already in progress and the network does not come back up. With the fixed version, network should be back up and the Suspend() call can be issued many times. Fix: https://github.com/desrt/systemd-shim/commit/136ed1143077d13c2 https://github.com/desrt/systemd-shim/commit/16a7fdc0652ad78f4 Regression potential: Errors in this code could potentially break suspend/shutdown completely, so for verification both of these functionalities ought to be tested on real hardware. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 891793] Re: Login with USB key or smart card
** Changed in: ltsp Importance: Undecided = Wishlist ** Changed in: ltsp Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/891793 Title: Login with USB key or smart card Status in Linux Terminal Server Project: Triaged Status in “gdm” package in Ubuntu: New Status in “lightdm” package in Ubuntu: Triaged Status in “lxdm” package in Ubuntu: New Status in “pam” package in Ubuntu: New Status in “sdm” package in Ubuntu: New Status in “seahorse” package in Ubuntu: New Status in “shadow” package in Ubuntu: New Status in “slim” package in Ubuntu: New Status in “wdm” package in Ubuntu: New Status in “xdm” package in Ubuntu: New Bug description: I want to be able to authenticate/login by using a USB key, SD/MMC card or a smart card. To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/891793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
It's great that Ubuntu 14.10 MATE beta is not affected by this bug. -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in ALT Linux: Unknown Status in “gnome-settings-daemon” package in Debian: New Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-settings-daemon” package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1245473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts
It's great that Ubuntu 14.10 MATE beta is not affected by this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1242572 Title: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts Status in central project for keyboard configuration: Fix Released Status in “console-setup” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “xkeyboard-config” package in Ubuntu: Confirmed Status in “console-setup” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Status in “xkeyboard-config” source package in Trusty: Confirmed Bug description: Super+Space is default combination for switching keyboard layouts in gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg; console-setup; and ubiquity should also use Super+Space combination for switching keyboard layouts. reading xkeyboard-config sources and documentations i don't see that xkeyboard-config can support grp:lwin_space and i guess that needs to be the first step to properly support super+space. Original bug report below: Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10. I use two keyboard layouts - English and Russian. So I select them on the corresponding screen of ubiquity setup wizard. It quietly set the keyboard switching shortcut to Alt+Shift and wrote this setting to /etc/default/keyboard: # ... XKBMODEL=pc105 XKBLAYOUT=us,ru XKBVARIANT=, XKBOPTIONS=grp:alt_shift_toggle,grp_led:scroll # ... On first boot of installed system the small notification pop-up showed that Ibus will use Super+Space for layout switching. Please fix this configuration inconsistency. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Mon Oct 21 12:16:58 2013 InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash -- InstallationDate: Installed on 2013-10-21 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131017) MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1
It's great that Ubuntu 14.10 MATE beta is not affected by this bug. -- 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/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-terminal” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Status in “openjdk-7” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Fedora: Unknown Status in “gnome-shell” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 206924] Re: Make it possible to create a guest account
** Changed in: ltsp Importance: Undecided = Wishlist ** Changed in: ltsp Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/206924 Title: Make it possible to create a guest account Status in D-Bus interfaces for querying and manipulating user account information: Confirmed Status in GDM: The Gnome Display Manager: Fix Released Status in GNOME Shutdown/Reboot/Suspend/Hibernate interface: Fix Released Status in Linux Terminal Server Project: Triaged Status in Xubuntu: New Status in “accountsservice” package in Ubuntu: Confirmed Status in “kde-workspace” package in Ubuntu: Won't Fix Status in “lxdm” package in Ubuntu: Opinion Status in “sdm” package in Ubuntu: Opinion Status in “slim” package in Ubuntu: Opinion Status in “wdm” package in Ubuntu: Opinion Status in “wing” package in Ubuntu: Opinion Status in “xdm” package in Ubuntu: Won't Fix Bug description: Make a guest account that people can login to, and check their mail, surf web, etc. Every time the guest account logs out, its purged so the next user who login is a clean fresh account. This would be great in public terminals, libraries, hotels, lobbys, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/206924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371960] [NEW] [VGN-TT11VN_X, Realtek ALC889, Black Headphone Out, Left] No sound at all
Public bug reported: I connect my headphones whith my laptop and expect to hear any Sound out of the headphones. The headphones were detected by the soundsytem. OK Speaker turn mute. OK But the headphones have no sound at all. lsb_release -rd: Description:Ubuntu 14.04.1 LTS Release:14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 20 20:02:37 2014 InstallationDate: Installed on 2014-08-03 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) 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: alexander 2024 F pulseaudio alexander 2988 F alsamixer Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [VGN-TT11VN_X, Realtek ALC889, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-09-20T19:47:04.327287 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1371960 Title: [VGN-TT11VN_X, Realtek ALC889, Black Headphone Out, Left] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: I connect my headphones whith my laptop and expect to hear any Sound out of the headphones. The headphones were detected by the soundsytem. OK Speaker turn mute. OK But the headphones have no sound at all. lsb_release -rd: Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 20 20:02:37 2014 InstallationDate: Installed on 2014-08-03 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) 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: alexander 2024 F pulseaudio alexander 2988 F alsamixer Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [VGN-TT11VN_X, Realtek ALC889, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-09-20T19:47:04.327287 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371960/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270579] Re: Ubuntu should have an init script for saving/restoring backlight level on laptops
Bug exists in Ubuntu 14.10 MATE beta. ** Also affects: ubuntu-mate Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1270579 Title: Ubuntu should have an init script for saving/restoring backlight level on laptops Status in elementary OS: New Status in One Hundred Papercuts: Confirmed Status in Ubuntu MATE: New Status in “sysvinit” package in Ubuntu: Confirmed Status in “sysvinit” package in Debian: New Bug description: I have tested many distros - Arch, OpenSuSe 13.1, Fedora 20, ALT Linux p7, Sabayon, Mageia 4. Many of them are based on systemd. It does not matter what init system they use, but all of them have very usefull script (or binary program, I don't know) for saving and restoring backlight level on laptop. In these distros there is a script for save and restore backlight levels for two video-cards (acpi_video0 and acpi_video1). During system boot it is indicated as follows: [ OK ] Started Load/Save Screen Backlight Brightness of acpi_video1. [ OK ] Started Load/Save Screen Backlight Brightness of acpi_video0. . I have a draft version, which works normally on my VAIO F13Z1R laptop with Ubuntu 12.04.4. It is in attachment. You can use it unmodified or modify it for compatibility or something. I made symlinks for it: ln -s /etc/init.d/brightness /etc/rc0.d/S25backlight ln -s /etc/init.d/brightness /etc/rcS.d/S25backlight ln -s /etc/init.d/brightness /etc/rc6.d/S25backlight For details you can read my comment on askubuntu (http://askubuntu.com/a/227553/66509). I think that having a script for saving and restoring backlight level is very useful for laptop Ubuntu users. So, please, add such init script to default Ubuntu installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1270579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371963] [NEW] cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC)
Public bug reported: Not very literate in Linux, had to disable Pulse Audio to get 5.1 sound to work. VLC will playback audio just fine by selecting sound card within the application. No/incorrect default sound card for system, cannot change through Gnome ALSA mixer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: king-clark 3060 F gnome-alsamixer /dev/snd/controlC1: king-clark 3060 F gnome-alsamixer /dev/snd/controlC0: king-clark 3060 F gnome-alsamixer CurrentDesktop: Unity Date: Sat Sep 20 14:11:11 2014 InstallationDate: Installed on 2013-12-03 (290 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to trusty on 2014-09-17 (3 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V32.12 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P33 Combo(MS-7592) dmi.board.vendor: MSI dmi.board.version: 7.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV32.12:bd09/13/2013:svnMSI:pnMS-7592:pvr7.0:rvnMSI:rnG41M-P33Combo(MS-7592):rvr7.0:cvnMSI:ct3:cvr7.0: dmi.product.name: MS-7592 dmi.product.version: 7.0 dmi.sys.vendor: MSI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1371963 Title: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC) Status in “alsa-driver” package in Ubuntu: New Bug description: Not very literate in Linux, had to disable Pulse Audio to get 5.1 sound to work. VLC will playback audio just fine by selecting sound card within the application. No/incorrect default sound card for system, cannot change through Gnome ALSA mixer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: king-clark 3060 F gnome-alsamixer /dev/snd/controlC1: king-clark 3060 F gnome-alsamixer /dev/snd/controlC0: king-clark 3060 F gnome-alsamixer CurrentDesktop: Unity Date: Sat Sep 20 14:11:11 2014 InstallationDate: Installed on 2013-12-03 (290 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to trusty on 2014-09-17 (3 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V32.12 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P33 Combo(MS-7592) dmi.board.vendor: MSI dmi.board.version: 7.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV32.12:bd09/13/2013:svnMSI:pnMS-7592:pvr7.0:rvnMSI:rnG41M-P33Combo(MS-7592):rvr7.0:cvnMSI:ct3:cvr7.0: dmi.product.name: MS-7592 dmi.product.version: 7.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350308] Re: Blank entries in transfer indicator
** Changed in: indicator-transfer (Ubuntu) Assignee: Charles Kerr (charlesk) = (unassigned) -- 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/1350308 Title: Blank entries in transfer indicator Status in “indicator-transfer” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: In Progress Bug description: Updating an app, and installing another i see no icon in transfer indicator and no text. See screenshot. Compare bug 1350771, the equivalent for in-progress updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-transfer/+bug/1350308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 293160] Re: sudo wont give up asking for you password even after several worng attempts or if you are not a sudoer
** Changed in: sudo (Ubuntu) Status: Invalid = Incomplete -- 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/293160 Title: sudo wont give up asking for you password even after several worng attempts or if you are not a sudoer Status in “sudo” package in Ubuntu: Incomplete Bug description: Binary package hint: sudo I have my Ubuntu 8.10 up to date (as in now) and I was trying a command (any command will do) with the wrong user (not a sudoer) under the sudo root-like privileges I would expect something like this if I type the wrong password: bzruser@ubuntu810:~$ sudo su - [sudo] password for bzruser: Sorry, try again. [sudo] password for bzruser: Sorry, try again. [sudo] password for bzruser: Sorry, try again. sudo: 3 incorrect password attempts Or this, if I do not type any password (just press enter): bzruser@ubuntu810:~$ sudo su - [sudo] password for bzruser: Or this, if I am not a sudoer: bzruser@ubuntu810:~$ sudo su - [sudo] password for bzruser: bzruser is not in the sudoers file. This incident will be reported. But instead, what I get is a never ending... [sudo] password for bzruser: No matter how many times I type or not the password, right or wrong... until I press a ^C (Ctrl+C) This used to work fine up until 8.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/293160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370758] Re: Sound settings lost after suspend
Hello, since pavucontrol is only GUI pulseaudio control app, i'm marking bug as Invalid in that package. ** Changed in: pavucontrol (Ubuntu) Status: New = Invalid -- 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/1370758 Title: Sound settings lost after suspend Status in “pavucontrol” package in Ubuntu: Invalid Status in “pulseaudio” package in Ubuntu: New Bug description: My dedault mic is usb camera. But after suspend default microphone is becoming empty IN in motherboard. Is there any other sound settings app for Xubuntu? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pavucontrol 2.0-2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 18 02:50:27 2014 InstallationDate: Installed on 2014-08-17 (31 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) SourcePackage: pavucontrol UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1370758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371642] Re: ADB over WIFI with Ubuntu Touch
Sorry for my decision, i didn't read it carefully. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1371642 Title: ADB over WIFI with Ubuntu Touch Status in “android-tools” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Bug description: There is currently no option to connect to an Ubuntu Touch device using ADB over WIFI. Some Android ROMs like Cyanogenmod support this feature and it comes in quite handy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1371642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371642] Re: ADB over WIFI with Ubuntu Touch
Hello, sorry for my decision. Afterwards, this don't actually affects android-tools, so i'm marking it as Invalid in android-tools. ** Changed in: android-tools (Ubuntu) Status: New = Invalid ** Changed in: ubuntu-system-settings (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1371642 Title: ADB over WIFI with Ubuntu Touch Status in “android-tools” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Bug description: There is currently no option to connect to an Ubuntu Touch device using ADB over WIFI. Some Android ROMs like Cyanogenmod support this feature and it comes in quite handy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1371642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370464] Re: yr.no changed the api version
** Bug watch added: GNOME Bug Tracker #736334 https://bugzilla.gnome.org/show_bug.cgi?id=736334 ** Also affects: libgweather via https://bugzilla.gnome.org/show_bug.cgi?id=736334 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1370464 Title: yr.no changed the api version Status in libgweather: Unknown Status in “libgweather” package in Ubuntu: New Bug description: yr.no, e.g. used as data source in the Gnome Shell extension weather (https://extensions.gnome.org/extension/613/weather/), changed its API version. Thus this extension does not work anymore: https://github.com/Neroth/gnome-shell-extension-weather/issues/208 Fixed already upstream for version 3.12, see https://bugzilla.gnome.org/show_bug.cgi?id=736334 Ubuntu version: 14.04 Package version: 3.10.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1370464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371454] Re: unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists hangs on mako #245 #246
ok, so for devel-proposed. I've at least determined this happened between image #235 (where AP would run to completion) image #237 (where is hangs). Worth noting, #136 impossible to work with, can't get adb to recognize the device no matter what. -- 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/1371454 Title: unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists hangs on mako #245 #246 Status in Media Hub: New Status in “unity8” package in Ubuntu: Opinion Bug description: Steps to reproduce - take * flash ubuntu-touch/devel-proposed reviosion 245 or later to mako * configure pin, developer mode, writable-image, network, .. * sudo apt-get install unity8-autopilot * sudo powerd-cli display on bright * autopilot run -v unity8-autopilot unity8 tests seem to run fine up to this point: 07:15:01.082 DEBUG __init__:305 - Unity started, waiting for it to be ready. 07:15:01.088 DEBUG dbus:433 - Selecting objects of type QQuickView with attributes: {} 07:15:01.185 DEBUG dbus:433 - Selecting objects of any type with attributes: {'objectName': 'greeterContentLoader'} 07:15:02.658 DEBUG __init__:307 - Unity loaded and ready. 07:15:02.659 DEBUG dbus:433 - Selecting objects of type QQuickView with attributes: {} 07:15:02.730 DEBUG dbus:433 - Selecting objects of type Greeter with attributes: {} 07:15:04.068 INFO process_helpers:95 - Greeter unlocked, continuing. 07:15:04.069 DEBUG dbus:433 - Selecting objects of type QQuickView with attributes: {} 07:15:04.166 DEBUG dbus:433 - Selecting objects of type DefaultIndicatorWidget with attributes: {'objectName': 'indicator-power-widget'} 07:15:05.095 INFO __init__:330 - Stopping unity 07:15:06.262 INFO __init__:246 - Resetting upstart env QT_LOAD_TESTABILITY to None 07:15:06.432 INFO testresult:46 - OK: unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists(Power,Native Device) 07:15:06.436 INFO globals:58 - 07:15:06.436 INFO globals:59 - Starting test unity8.indicators.tests.test_indicators.IndicatorExistsTestCase.test_indicator_exists (Sound,Native Device) 07:15:06.438 WARNING testcase:116 - No tracing available - install the python-autopilot-trace package! 07:15:06.443 WARNING testcase:157 - Process manager backend unavailable, application snapshot support disabled. 07:15:06.452 WARNING utilities:265 - WARNING: in file /usr/lib/python2.7/dist-packages/unity8/shell/tests/__init__.py, line 164 in setUp This function is deprecated. Please use 'the Touch class to instantiate a device object' instead. 07:15:06.727 INFO __init__:268 - Lib path is '/usr/lib/arm-linux-gnueabihf/unity8', binary path is '/usr/bin/unity8' 07:15:06.729 INFO __init__:346 - Setting up LightDM mock type 'single' 07:15:06.837 INFO __init__:355 - New library path: /usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single 07:15:06.884 INFO __init__:108 - New QML2 import path: /usr/lib/arm-linux-gnueabihf/unity8/qml/mocks 07:15:06.951 INFO __init__:317 - Starting unity 07:15:07.047 INFO process_helpers:151 - Starting job unity8 with arguments ('BINARY=/usr/bin/unity8', 'ARGS=', 'XDG_DATA_DIRS=/usr/share/unity8/mocks/data:/usr/share/ubuntu-touch:/usr/local/share:/usr/share', 'LD_LIBRARY_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/libusermetrics:/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks/LightDM/single', 'QML2_IMPORT_PATH=/usr/lib/arm-linux-gnueabihf/unity8/qml/mocks', 'QT_LOAD_TESTABILITY=1'). 07:15:07.679 INFO process_helpers:159 - unity8 start/running, process 7450 07:15:33.540 ERROR proxies:410 - Introspect error on :1.391:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 07:15:33.547 DEBUG proxies:413 - Executing introspect queue due to error 07:16:25.189 ERROR proxies:410 - Introspect error on :1.413:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 07:16:25.195 DEBUG proxies:413 - Executing introspect queue due to error 07:17:15.309 ERROR proxies:410 - Introspect error on :1.391:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the
[Touch-packages] [Bug 1371977] [NEW] [Alienware 17, Realtek ALC668, Speaker, Internal] No sound at all
Public bug reported: First this was the problem and i did as it was given in some others report and the sound was working but after installing some other softwares it stopped working again ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max2163 F pulseaudio /dev/snd/controlC1: max2163 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 21 01:57:56 2014 InstallationDate: Installed on 2014-08-19 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max2163 F pulseaudio /dev/snd/controlC1: max2163 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Alienware 17, Realtek ALC668, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2014 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd02/25/2014:svnAlienware:pnAlienware17:pvrA09:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA09: dmi.product.name: Alienware 17 dmi.product.version: A09 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-09-20T13:56:34.698572 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1371977 Title: [Alienware 17, Realtek ALC668, Speaker, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: First this was the problem and i did as it was given in some others report and the sound was working but after installing some other softwares it stopped working again ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max2163 F pulseaudio /dev/snd/controlC1: max2163 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 21 01:57:56 2014 InstallationDate: Installed on 2014-08-19 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max2163 F pulseaudio /dev/snd/controlC1: max2163 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Alienware 17, Realtek ALC668, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2014 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: 068R5X dmi.board.vendor: Alienware dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd02/25/2014:svnAlienware:pnAlienware17:pvrA09:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA09: dmi.product.name: Alienware 17 dmi.product.version: A09 dmi.sys.vendor: Alienware mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-09-20T13:56:34.698572 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1309141] Re: Apt is missing tab complete on things like list search etc
** Bug watch added: Debian Bug tracker #762286 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762286 ** Also affects: apt (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762286 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1309141 Title: Apt is missing tab complete on things like list search etc Status in APT: Unknown Status in “apt” package in Ubuntu: In Progress Status in “apt” package in Debian: Unknown Bug description: Before I could do apt-gtab upgrtab and hit enter and be done With the new apt I can nolonger do this instead I have to type in apt search/list/update/upgrade/full-upgrade etc ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 17 19:30:35 2014 InstallationDate: Installed on 2014-04-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1309141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324399] Re: apt-get failing to show progress with yes command
** Tags removed: verification-done ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1324399 Title: apt-get failing to show progress with yes command Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Trusty: In Progress Bug description: When running this command on Ubuntu 14.04 amd64 release: yes | apt-get -y install tftpd-hpa It never finishes... Only shows black screen on the terminal. I know it's weird to use yes for this command. However, just to show it does not make any sense the command can not be finished. This issue does not occur on Ubuntu 13.10, nor on Debian Sid. The following is some info about this system: ProblemType: Bug ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Thu May 29 15:06:52 2014 Dependencies: dpkg 1.17.5ubuntu5.2 gcc-4.8-base 4.8.2-19ubuntu1 gcc-4.9-base 4.9-20140406-0ubuntu1 gnupg 1.4.16-1ubuntu2 gpgv 1.4.16-1ubuntu2 libacl1 2.2.52-1 libapt-pkg4.12 1.0.1ubuntu2 libattr1 1:2.4.47-1ubuntu1 libbz2-1.0 1.0.6-5 libc6 2.19-0ubuntu6 libgcc1 1:4.9-20140406-0ubuntu1 liblzma5 5.1.1alpha+20120614-2ubuntu2 libpcre3 1:8.31-2ubuntu2 libreadline6 6.3-4ubuntu2 libselinux1 2.2.2-1ubuntu0.1 libstdc++6 4.8.2-19ubuntu1 libtinfo5 5.9+20140118-1ubuntu1 libusb-0.1-4 2:0.1.12-23.3ubuntu1 multiarch-support 2.19-0ubuntu6 readline-common 6.3-4ubuntu2 tar 1.27.1-1 ubuntu-keyring 2012.05.19 zlib1g 1:1.2.8.dfsg-1ubuntu1 DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 SourcePackage: apt Tags: trusty Uname: Linux 3.13.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1324399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1274466] Re: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields
** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1274466 Title: apt-ftparchive on-disk cache format changed between lucid and precise, results in Packages files with silently corrupted checksums fields Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Precise: In Progress Status in “apt” source package in Trusty: In Progress Bug description: TEST CASE: 1. generate a cachedb with apt-ftparchive from lucid via apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.1 - use apt-ftparchive from precise and run apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.2 and verify that it generates different hashes than Packages.1 (diff -u Packages.1 Packages.2) - use apt-ftparchive from precise-proposed and run: apt-ftparchive --db old-db packages 2vcard_0.5-3_all.deb Packages.3 and verify that the hashes are identical to the ones in Packages.1 The archive.ubuntu.com master server has just been upgraded from lucid to precise. As a result, the apt version went from 0.7.25.3 to 0.8.16~exp12, and apparently some time in that interval the on-disk format of apt-ftparchive's cache changed. This wouldn't be a problem, except apt-ftparchive itself doesn't *notice* that the cache format has changed, and instead happily reads the existing files and parses them incorrectly, resulting in corrupted checksums output in the Packages file for each of the .debs. apt-ftparchive should version its file formats so that it correctly notices incompatible cache files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1274466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329212] Re: apt-ftparchive should support a cachedb for source packages
** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1329212 Title: apt-ftparchive should support a cachedb for source packages Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Trusty: In Progress Bug description: The apt-ftparchive tool should support a cachedb for the source packages just like it does for the binary packages. TEST CASE: - test that there are no regression for a existing archive by generating Packages/Sources files from a cachedb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1329212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358134] Re: Bluetooth unable to receive files from phone
This same bluez version works with Ubuntu 14.10 current-daily-amd64 as of 20 September. Bluez pairs, connects and is able to stream a2dp stereo audio to my BT headset. This leads me to believe that the issues with Bluetooth audio streaming aren't with bluez - perhaps PulseAudio or another package. This bug should be marked 'Invalid'. ** Changed in: bluez (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1358134 Title: Bluetooth unable to receive files from phone Status in “bluez” package in Ubuntu: Invalid Bug description: Ubuntu 14.04.1 64-bit: Bluetooth will not receive photos or files from HTC Rezound running Android 4.0.3 OEM. I can browse files on the phone, but cannot use them (copy, transfer, etc.). If I attempt to transfer files from phone to PC, I get anOBEX error message. I also occasionally see an input/output error message. Bluetooth can send files to the phone. Lubuntu 14.04.1 running from Live-USB is able to send receive files photos successfully on the same hardware. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 18 01:33:24 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-08-09 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1358134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371989] [NEW] After update not recognize sound card
Public bug reported: After update and restart (Ubuntu 12.04.5 64bit) not angnorizei sound card and quote the output of the command dmesg : init: alsa-restore main process (1037) terminated with status 99 AND Your ALSA information is located at http://www.alsa-project.org/db/?f=fb3b9540d8340b693dba88a3696959ced13cafc5 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- 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/1371989 Title: After update not recognize sound card Status in “alsa-driver” package in Ubuntu: New Bug description: After update and restart (Ubuntu 12.04.5 64bit) not angnorizei sound card and quote the output of the command dmesg : init: alsa-restore main process (1037) terminated with status 99 AND Your ALSA information is located at http://www.alsa-project.org/db/?f=fb3b9540d8340b693dba88a3696959ced13cafc5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371989] Re: After update not recognize sound card
** Description changed: - After update and restart (Ubuntu 12.04.5 64bit) not angnorizei sound - card and quote the output of the command dmesg : + After update and restart (Ubuntu 12.04.5 64bit) not recognize the + sound card and quote the output of the command dmesg : init: alsa-restore main process (1037) terminated with status 99 - AND + AND Your ALSA information is located at http://www.alsa-project.org/db/?f=fb3b9540d8340b693dba88a3696959ced13cafc5 -- 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/1371989 Title: After update not recognize sound card Status in “alsa-driver” package in Ubuntu: New Bug description: After update and restart (Ubuntu 12.04.5 64bit) not recognize the sound card and quote the output of the command dmesg : init: alsa-restore main process (1037) terminated with status 99 AND Your ALSA information is located at http://www.alsa-project.org/db/?f=fb3b9540d8340b693dba88a3696959ced13cafc5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371991] [NEW] FFe: Sync libassuan 2.1.2-2 (main) from Debian unstable (main)
Public bug reported: Please sync libassuan 2.1.2-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Build using dh-autoreconf. Fixed in debian Explanation of FeatureFreeze exception: New upstream release that's only change is adding ppc64le support Changelog entries since current utopic version 2.1.1-1ubuntu1: libassuan (2.1.2-2) unstable; urgency=medium * debian/control: Switch maintainer to Debian GnuPG-Maintainers. * debian/control: Move to new pkg-gnupg git repository. * Run wrap-and-sort on debian directory. Thanks dkg for showing me this tool. * debian/gbp.conf: Add git-buildpackage config and turn on pristine-tar. -- Eric Dorland e...@debian.org Sat, 30 Aug 2014 21:52:31 -0400 libassuan (2.1.2-1) unstable; urgency=medium * New upstream release. -- Eric Dorland e...@debian.org Sat, 23 Aug 2014 22:38:46 -0400 libassuan (2.1.1-2) unstable; urgency=low * debian/control: Canonicalize Vcs-Browser field. * debian/watch, debian/upstream/signing-key.asc: Add upstream signing key for the watch file. * debian/control: Fix descriptions to be more descriptive. * debian/control: Upgrade Standards-Version to 3.9.5. * debian/control, debian/rules: Use dh-autoreconf. (Closes: #752025) -- Eric Dorland e...@debian.org Sat, 23 Aug 2014 22:26:58 -0400 ** Affects: libassuan (Ubuntu) Importance: Wishlist Status: New ** Changed in: libassuan (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libassuan in Ubuntu. https://bugs.launchpad.net/bugs/1371991 Title: FFe: Sync libassuan 2.1.2-2 (main) from Debian unstable (main) Status in “libassuan” package in Ubuntu: New Bug description: Please sync libassuan 2.1.2-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Build using dh-autoreconf. Fixed in debian Explanation of FeatureFreeze exception: New upstream release that's only change is adding ppc64le support Changelog entries since current utopic version 2.1.1-1ubuntu1: libassuan (2.1.2-2) unstable; urgency=medium * debian/control: Switch maintainer to Debian GnuPG-Maintainers. * debian/control: Move to new pkg-gnupg git repository. * Run wrap-and-sort on debian directory. Thanks dkg for showing me this tool. * debian/gbp.conf: Add git-buildpackage config and turn on pristine-tar. -- Eric Dorland e...@debian.org Sat, 30 Aug 2014 21:52:31 -0400 libassuan (2.1.2-1) unstable; urgency=medium * New upstream release. -- Eric Dorland e...@debian.org Sat, 23 Aug 2014 22:38:46 -0400 libassuan (2.1.1-2) unstable; urgency=low * debian/control: Canonicalize Vcs-Browser field. * debian/watch, debian/upstream/signing-key.asc: Add upstream signing key for the watch file. * debian/control: Fix descriptions to be more descriptive. * debian/control: Upgrade Standards-Version to 3.9.5. * debian/control, debian/rules: Use dh-autoreconf. (Closes: #752025) -- Eric Dorland e...@debian.org Sat, 23 Aug 2014 22:26:58 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libassuan/+bug/1371991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358134] Re: Bluetooth unable to receive files from phone
** Changed in: bluez (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1358134 Title: Bluetooth unable to receive files from phone Status in “bluez” package in Ubuntu: New Bug description: Ubuntu 14.04.1 64-bit: Bluetooth will not receive photos or files from HTC Rezound running Android 4.0.3 OEM. I can browse files on the phone, but cannot use them (copy, transfer, etc.). If I attempt to transfer files from phone to PC, I get anOBEX error message. I also occasionally see an input/output error message. Bluetooth can send files to the phone. Lubuntu 14.04.1 running from Live-USB is able to send receive files photos successfully on the same hardware. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 18 01:33:24 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-08-09 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1358134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358134] Re: Bluetooth unable to receive files from phone
I got sidetracked with audio issues - mea culpa - original issue of being unable to send photos from my phone to my PC still exist in 14.04 as well as 14.10 daily-current-amd64 as of 20 September. I can browse the phone folders from my PC but cannot do anything with those files from the PC. I am able to transfer files from the PC to the phone. The PC never pops up a window asking if I want to accept the files I attempt to send from my phone, even though the phone is paired and connected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1358134 Title: Bluetooth unable to receive files from phone Status in “bluez” package in Ubuntu: New Bug description: Ubuntu 14.04.1 64-bit: Bluetooth will not receive photos or files from HTC Rezound running Android 4.0.3 OEM. I can browse files on the phone, but cannot use them (copy, transfer, etc.). If I attempt to transfer files from phone to PC, I get anOBEX error message. I also occasionally see an input/output error message. Bluetooth can send files to the phone. Lubuntu 14.04.1 running from Live-USB is able to send receive files photos successfully on the same hardware. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 18 01:33:24 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-08-09 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1358134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1309141] Re: Apt is missing tab complete on things like list search etc
** Changed in: apt (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1309141 Title: Apt is missing tab complete on things like list search etc Status in APT: Unknown Status in “apt” package in Ubuntu: In Progress Status in “apt” package in Debian: New Bug description: Before I could do apt-gtab upgrtab and hit enter and be done With the new apt I can nolonger do this instead I have to type in apt search/list/update/upgrade/full-upgrade etc ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 17 19:30:35 2014 InstallationDate: Installed on 2014-04-17 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1309141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372006] [NEW] pci_devices does not terminate at computer shutdown
Public bug reported: Shutdown does not halt on my Dell Precision 390 the shutdown sequence prints on the console: mount: / is busy /etc/init.d/sendsigs does not terminate systemd-udevd Only solution: enable and use ALT-SYSREQ REISUB (to keep the root fs clean) I tried to change GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub (+ update-grub): GRUB_CMDLINE_LINUX_DEFAULT=quiet nosplash reboot=pci or GRUB_CMDLINE_LINUX_DEFAULT=quiet nosplash reboot=bios or GRUB_CMDLINE_LINUX_DEFAULT=quiet nosplash acpi=force Shutdown still hangs with 'mount: / is busy' I even updated the BIOS from 2.0.4 to 2.06, no luck. When booting from a Knoppix 6.0.1 CD with a 2.6 kernel, shutdown works and halts the system to poweroff state. Any ideas? Thanks ahau ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Sun Sep 21 02:58:10 2014 ExecutablePath: /usr/lib/pm-utils/power.d/pci_devices InstallationDate: Installed on 2014-09-19 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) InterpreterPath: /bin/dash OmitPids: 11761 308 302 11767 723 714 11890 11767 723 714 11890 PackageArchitecture: all ProcCmdline: /bin/sh /usr/lib/pm-utils/power.d/pci_devices false ProcEnviron: LC_COLLATE=C PATH=(custom, no user) SourcePackage: pm-utils Title: pci_devices does not terminate at computer shutdown UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug shutdown-hang trusty -- 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/1372006 Title: pci_devices does not terminate at computer shutdown Status in “pm-utils” package in Ubuntu: New Bug description: Shutdown does not halt on my Dell Precision 390 the shutdown sequence prints on the console: mount: / is busy /etc/init.d/sendsigs does not terminate systemd-udevd Only solution: enable and use ALT-SYSREQ REISUB (to keep the root fs clean) I tried to change GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub (+ update-grub): GRUB_CMDLINE_LINUX_DEFAULT=quiet nosplash reboot=pci or GRUB_CMDLINE_LINUX_DEFAULT=quiet nosplash reboot=bios or GRUB_CMDLINE_LINUX_DEFAULT=quiet nosplash acpi=force Shutdown still hangs with 'mount: / is busy' I even updated the BIOS from 2.0.4 to 2.06, no luck. When booting from a Knoppix 6.0.1 CD with a 2.6 kernel, shutdown works and halts the system to poweroff state. Any ideas? Thanks ahau ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Sun Sep 21 02:58:10 2014 ExecutablePath: /usr/lib/pm-utils/power.d/pci_devices InstallationDate: Installed on 2014-09-19 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) InterpreterPath: /bin/dash OmitPids: 11761 308 302 11767 723 714 11890 11767 723 714 11890 PackageArchitecture: all ProcCmdline: /bin/sh /usr/lib/pm-utils/power.d/pci_devices false ProcEnviron: LC_COLLATE=C PATH=(custom, no user) SourcePackage: pm-utils Title: pci_devices does not terminate at computer shutdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1372006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372011] [NEW] ListItem.Subtitled subText color is too dark with SuruDark
Public bug reported: It is hard to read ListItem.Subtitled subText when using the SuruDark theme (or other dark themes). ** Affects: permy Importance: Undecided Status: New ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: permy Importance: Undecided Status: 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/1372011 Title: ListItem.Subtitled subText color is too dark with SuruDark Status in Permy: New Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: It is hard to read ListItem.Subtitled subText when using the SuruDark theme (or other dark themes). To manage notifications about this bug go to: https://bugs.launchpad.net/permy/+bug/1372011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
** Changed in: fonts-android (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Status in “fonts-android” package in Debian: Fix Released Bug description: [Impact] fontconfig configuration settings, aimed at making the Droid Sans Fallback font be used to render Chinese, fails sometimes in an unpredictable way. This seems to be caused by the file 65-droid-sans- fonts.conf, which is currently installed by fonts-droid. Consequently that file is proposed to be dropped from fonts-droid. Some fontconfig files in language-selector are proposed to be changed accordingly. Example problems: * One of the AR PL UMing fonts is sometimes used instead of Droid Sans Fallback in case of a Chinese locale. * Buggy rendering of Chinese contents in qt apps in case of a non-Chinese locale (bug #1334495). * Droid Sans Fallback can't be used in Ubuntu Touch (see discussion at bug #1346766). [Test Case] Since the behaviour is not always buggy, it's hard to present a proper test case. Instead I have to refer to the discussions in this bug report as well as the above mentioned bugs. [Regression Potential] While the fonts-droid package installs a bunch of fonts for various languages, only the Droid Sans Fallback font is used as part of Ubuntu's default font configuration. The regression risk for Chinese users is reasonably very low. There is a risk, though, that this change leads to surprise changes for individual users who make use of other fonts but Droid Sans Fallback. There is no indication that those other fonts are widely used. [Original description] There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: Droid Sans Fallback Regular uming.ttc: AR PL UMing CN Light uming.ttc: AR PL UMing HK Light ukai.ttc: AR PL UKai CN Book DejaVuSans.ttf: DejaVu Sans Book Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372013] [NEW] package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
Public bug reported: while upgrading 13.10 to 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dictionaries-common 1.20.5 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Sat Sep 20 23:30:33 2014 DuplicateSignature: package:dictionaries-common:1.20.5:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 PackageArchitecture: all SourcePackage: dictionaries-common Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: Upgraded to trusty on 2014-09-21 (0 days ago) ** Affects: dictionaries-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1372013 Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in “dictionaries-common” package in Ubuntu: New Bug description: while upgrading 13.10 to 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dictionaries-common 1.20.5 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Sat Sep 20 23:30:33 2014 DuplicateSignature: package:dictionaries-common:1.20.5:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 PackageArchitecture: all SourcePackage: dictionaries-common Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: Upgraded to trusty on 2014-09-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1372013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368420] Re: Prices shown incorrectly in some locales
** Also affects: libjsoncpp (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: libjsoncpp (Ubuntu RTM) Assignee: (unassigned) = Rodney Dawes (dobey) ** Changed in: libjsoncpp (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: libjsoncpp (Ubuntu RTM) 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/1368420 Title: Prices shown incorrectly in some locales Status in “libjsoncpp” package in Ubuntu: Fix Released Status in “unity-scope-click” package in Ubuntu: Invalid Status in “libjsoncpp” package in Ubuntu RTM: In Progress Bug description: In some locales, some prices seem to be shown incorrectly. For example, a price of 2.99 for an app is being shown as 2,00 when using the Spanish locale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/1368420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371963] Re: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC)
5.1 is only available after you change the channel mode from 2ch to 6ch which retask blue line in and pink mic Jack as output, before pulseaudio probe the sound card during startup Simple mixer control 'Channel Mode',0 Capabilities: enum Items: '2ch' '4ch' '6ch' Item0: '2ch' this mean you have to change the channel mode and restart pulseaudio -- 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/1371963 Title: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC) Status in “alsa-driver” package in Ubuntu: New Bug description: Not very literate in Linux, had to disable Pulse Audio to get 5.1 sound to work. VLC will playback audio just fine by selecting sound card within the application. No/incorrect default sound card for system, cannot change through Gnome ALSA mixer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: king-clark 3060 F gnome-alsamixer /dev/snd/controlC1: king-clark 3060 F gnome-alsamixer /dev/snd/controlC0: king-clark 3060 F gnome-alsamixer CurrentDesktop: Unity Date: Sat Sep 20 14:11:11 2014 InstallationDate: Installed on 2013-12-03 (290 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to trusty on 2014-09-17 (3 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V32.12 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P33 Combo(MS-7592) dmi.board.vendor: MSI dmi.board.version: 7.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV32.12:bd09/13/2013:svnMSI:pnMS-7592:pvr7.0:rvnMSI:rnG41M-P33Combo(MS-7592):rvr7.0:cvnMSI:ct3:cvr7.0: dmi.product.name: MS-7592 dmi.product.version: 7.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371963] Re: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC)
change channel mode to 6ch save the setting by alsactl store at next reboot/login alsactl restore before starting pulseaudio -- 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/1371963 Title: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC) Status in “alsa-driver” package in Ubuntu: New Bug description: Not very literate in Linux, had to disable Pulse Audio to get 5.1 sound to work. VLC will playback audio just fine by selecting sound card within the application. No/incorrect default sound card for system, cannot change through Gnome ALSA mixer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: king-clark 3060 F gnome-alsamixer /dev/snd/controlC1: king-clark 3060 F gnome-alsamixer /dev/snd/controlC0: king-clark 3060 F gnome-alsamixer CurrentDesktop: Unity Date: Sat Sep 20 14:11:11 2014 InstallationDate: Installed on 2013-12-03 (290 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to trusty on 2014-09-17 (3 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V32.12 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P33 Combo(MS-7592) dmi.board.vendor: MSI dmi.board.version: 7.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV32.12:bd09/13/2013:svnMSI:pnMS-7592:pvr7.0:rvnMSI:rnG41M-P33Combo(MS-7592):rvr7.0:cvnMSI:ct3:cvr7.0: dmi.product.name: MS-7592 dmi.product.version: 7.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371963] Re: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC)
did you plug all your 5.1 speakers ? the main problem are the Jack state of the rear Mic jack and line in Jack become true and pulseaudio caanot determine the default source control.34 { iface CARD name 'Rear Mic Jack' value false comment { access read type BOOLEAN count 1 } } control.35 { iface CARD name 'Line Jack' value false comment { access read type BOOLEAN count 1 } } -- 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/1371963 Title: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC) Status in “alsa-driver” package in Ubuntu: New Bug description: Not very literate in Linux, had to disable Pulse Audio to get 5.1 sound to work. VLC will playback audio just fine by selecting sound card within the application. No/incorrect default sound card for system, cannot change through Gnome ALSA mixer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: king-clark 3060 F gnome-alsamixer /dev/snd/controlC1: king-clark 3060 F gnome-alsamixer /dev/snd/controlC0: king-clark 3060 F gnome-alsamixer CurrentDesktop: Unity Date: Sat Sep 20 14:11:11 2014 InstallationDate: Installed on 2013-12-03 (290 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to trusty on 2014-09-17 (3 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V32.12 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P33 Combo(MS-7592) dmi.board.vendor: MSI dmi.board.version: 7.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV32.12:bd09/13/2013:svnMSI:pnMS-7592:pvr7.0:rvnMSI:rnG41M-P33Combo(MS-7592):rvr7.0:cvnMSI:ct3:cvr7.0: dmi.product.name: MS-7592 dmi.product.version: 7.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1061069]
FYI: CUPS 1.7.5 is available from OBS home project home:jsmeix. cups-filters 1.0.58 is available from OBS devel project Printing. See also comment#62 above. -- 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/1061069 Title: CUPS 1.6 has major incompatible changes. Do not use CUPS 1.6.1 on stable Ubuntu releases Status in “cups” package in Ubuntu: Fix Released Status in “cups-filters” package in Ubuntu: Fix Released Status in “cups” source package in Quantal: Fix Released Status in “cups-filters” source package in Quantal: Invalid Status in “cups” source package in Raring: Fix Released Status in “cups-filters” source package in Raring: Fix Released Status in “cups” package in Suse: Confirmed Bug description: Drastic changes in CUPS 1.6.1 (non Apple feature removed mostly) are detrimental to Ubuntu users. We should wait until the missing features (like automatic appearing of remote CUPS queues) before to unleash the newer version to users. This means downgrading cups in Quantal. See LP Bug 1061063 and Bug 1052897 for examples and the big list on Suse bugzilla : https://bugzilla.novell.com/show_bug.cgi?id=735404 for more informations. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CupsErrorLog: W [03/Oct/2012:07:36:11 +0200] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP_LaserJet_P3010-Gray..' already exists W [03/Oct/2012:07:36:11 +0200] CreateDevice failed: org.freedesktop.ColorManager.AlreadyExists:device id 'cups-HP_LaserJet_P3010' already exists Date: Wed Oct 3 18:23:44 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120911) Lpstat: device for Brother: dnssd://Brother%20QL-570%20%40%20gland._ipp._tcp.local/cups device for HP_LaserJet_P3010: hp:/net/HP_LaserJet_P3010_Series?zc=laserjet MachineType: LENOVO 4293AA6 Papersize: a4 PpdFiles: HP_LaserJet_P3010: HP LaserJet P3010 Series Postscript (recommended) ProcEnviron: LANGUAGE=fr_CH:fr TERM=xterm PATH=(custom, no user) LANG=fr_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-16-generic root=UUID=529c6222-fe36-40b3-9692-581c477062a4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET61WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 4293AA6 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:bvr8DET61WW(1.31):bd04/25/2012:svnLENOVO:pn4293AA6:pvrThinkPadX220:rvnLENOVO:rn4293AA6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4293AA6 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO modified.conffile..etc.cups.cupsd.conf: [modified] mtime.conffile..etc.cups.cupsd.conf: 2012-10-02T11:11:41.190220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1061069/+subscriptions -- Mailing list: https://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 1371963] Re: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC)
I got it working. The issue was with the spdif optical output on my secondary audio card. Pulse audio initially would not output 5.1 so I disabled it and tried ALSA. I was then able to output 5.1 in VLC but I was not able to get any audio to output elsewhere. After trying multiple ALSA mixers to no avail, I reinstalled pulse audio and viola, I retained 5.1 output in VLC through ALSA and now have stereo output via pulse audio for all other applications. Thank you for your help! On Sep 21, 2014 12:01 AM, Raymond 1371...@bugs.launchpad.net wrote: did you plug all your 5.1 speakers ? the main problem are the Jack state of the rear Mic jack and line in Jack become true and pulseaudio caanot determine the default source control.34 { iface CARD name 'Rear Mic Jack' value false comment { access read type BOOLEAN count 1 } } control.35 { iface CARD name 'Line Jack' value false comment { access read type BOOLEAN count 1 } } -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1371963 Title: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC) Status in “alsa-driver” package in Ubuntu: New Bug description: Not very literate in Linux, had to disable Pulse Audio to get 5.1 sound to work. VLC will playback audio just fine by selecting sound card within the application. No/incorrect default sound card for system, cannot change through Gnome ALSA mixer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: king-clark 3060 F gnome-alsamixer /dev/snd/controlC1: king-clark 3060 F gnome-alsamixer /dev/snd/controlC0: king-clark 3060 F gnome-alsamixer CurrentDesktop: Unity Date: Sat Sep 20 14:11:11 2014 InstallationDate: Installed on 2013-12-03 (290 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: Upgraded to trusty on 2014-09-17 (3 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V32.12 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-P33 Combo(MS-7592) dmi.board.vendor: MSI dmi.board.version: 7.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV32.12:bd09/13/2013:svnMSI:pnMS-7592:pvr7.0:rvnMSI:rnG41M-P33Combo(MS-7592):rvr7.0:cvnMSI:ct3:cvr7.0: dmi.product.name: MS-7592 dmi.product.version: 7.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1371963/+subscriptions -- 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/1371963 Title: cannot set default audio device with alsa (pulse audio disabled, can only get audio to work in VLC) Status in “alsa-driver” package in Ubuntu: New Bug description: Not very literate in Linux, had to disable Pulse Audio to get 5.1 sound to work. VLC will playback audio just fine by selecting sound card within the application. No/incorrect default sound card for system, cannot change through Gnome ALSA mixer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: king-clark 3060 F gnome-alsamixer /dev/snd/controlC1: king-clark 3060 F gnome-alsamixer /dev/snd/controlC0: king-clark 3060 F gnome-alsamixer CurrentDesktop: Unity Date: Sat Sep 20 14:11:11 2014 InstallationDate: Installed on 2013-12-03 (290 days ago)
[Touch-packages] [Bug 1372013] Re: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
** Attachment removed: VarLogDistupgradeTermlog.gz https://bugs.launchpad.net/bugs/1372013/+attachment/4210184/+files/VarLogDistupgradeTermlog.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1372013 Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in “dictionaries-common” package in Ubuntu: New Bug description: while upgrading 13.10 to 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dictionaries-common 1.20.5 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Sat Sep 20 23:30:33 2014 DuplicateSignature: package:dictionaries-common:1.20.5:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 PackageArchitecture: all SourcePackage: dictionaries-common Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: Upgraded to trusty on 2014-09-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1372013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372013] Re: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dictionaries-common in Ubuntu. https://bugs.launchpad.net/bugs/1372013 Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 Status in “dictionaries-common” package in Ubuntu: New Bug description: while upgrading 13.10 to 14.04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: dictionaries-common 1.20.5 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Sat Sep 20 23:30:33 2014 DuplicateSignature: package:dictionaries-common:1.20.5:subprocess installed post-installation script returned error exit status 255 ErrorMessage: subprocess installed post-installation script returned error exit status 255 PackageArchitecture: all SourcePackage: dictionaries-common Title: package dictionaries-common 1.20.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 UpgradeStatus: Upgraded to trusty on 2014-09-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1372013/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
[Expired for sudo (Ubuntu) because there has been no activity for 60 days.] ** Changed in: sudo (Ubuntu) Status: Incomplete = Expired -- 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: Expired 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 1346428] Re: [HDA-Intel - HDA Intel, playback] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1346428 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in “alsa-driver” package in Ubuntu: Expired 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 1345447] Re: [Asus Sabertooth 990FX R2.0, Realtek ALC892 [1002:4383] ] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1345447 Title: [Asus Sabertooth 990FX R2.0, Realtek ALC892 [1002:4383] ] No sound at all Status in “alsa-driver” package in Ubuntu: Expired 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 1351227] Re: libwebp ftbfs on arm64
** Branch linked: lp:debian/gnat-4.9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1351227 Title: libwebp ftbfs on arm64 Status in The GNU Compiler Collection: Invalid Status in “gcc-4.9” package in Ubuntu: Fix Released Status in “libwebp” package in Ubuntu: Confirmed Bug description: ICE To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1351227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347147] Re: krb5 database operations enter infinite loop
** Branch linked: lp:debian/gnat-4.9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1347147 Title: krb5 database operations enter infinite loop Status in The GNU Compiler Collection: Fix Released Status in Network Authentication System: Unknown Status in “gcc-4.8” package in Ubuntu: Fix Released Status in “gcc-4.9” package in Ubuntu: Fix Released Status in “krb5” package in Ubuntu: Fix Released Status in “gcc-4.8” source package in Trusty: Confirmed Status in “krb5” source package in Trusty: Triaged Bug description: [Impact] On krb5 KDC databases with more than a few hundred principals, operations can enter an infinite loop in the database library. This affects both read and write operations. If operators are fortunate, they will encounter this bug while testing a migration. If they are not so fortunate, they will encounter this bug in a production KDC when the number of principals crosses the threshold where this bug manifests, resulting in a service outage and possible database corruption. Probably the only way to restore service in that situation is to install a patched KDC or to downgrade to an unaffected version. Both Trusty and Utopic amd64 have been verified to have this issue. One concrete reported example is an invocation of kdb5_util load (as part of a slave KDC propagation) spinning: http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html Additional failure modes are likely A branch is linked including the upstream work around for this bug, along with two other patches to bugs already nominated for trusty applied to the krb5 in trusty. For utopic, the simplest fix is to rebuild krb5 with the compiler currently in utopic. An alternative is to request that the Debian maintainers (both monitoring this bug for such a request) upload the upstream work around to Debian and sync that. You could do an ubuntu- specific upload but it seems undesirable to introduce a change between Ubuntu and Debian when all the right parties are happy to avoid it. The upstream patch works around a compiler optimizer bug in the gcc-4.8 series, which incorrectly deduces that a strict aliasing violation has occurred and miscompiles part of the bundled libdb2 library that the KDC database back end depends upon. The miscompilation causes a data structure to contain an inappropriate cycle, which leads to an infinite loop when the structure is traversed. [Test Case] apt-get install krb5-kdc krb5-admin-server kdb5_util -W -r T create -s awk 'BEGIN{ for (i = 0; i 1024; i++) { printf(ank -randkey a%06d\n, i) } }' /dev/null | kadmin.local -r T (Enter any password for the master key when requested.) On platforms with this issue, kadmin.local spins consuming 100% CPU after a few hundred principals have been created. (This is a000762 on two examples.) To clean up, rm /etc/krb5kdc/principal* or krb5kdc -r T destroy but the latter can possibly enter the same infinite loop. [Regression Potential] Negligible. It is theoretically possible that our upstream workaround, which involves using TAILQ macros instead of CIRCLEQ macros in the bundled libdb2 that backs the KDC database, will have some as-yet undiscovered bugs or compiler interactions with consequences worse than this current issue. I think this is rather unlikely. The patched libdb2 passes both the extensive libdb2 test suite and the rest of the krb5 test suite. Prior to patching, compiling krb5 with an affected gcc would cause the krb5 test suite to stall when it reached the libdb2 test suite. (The test suite stall is how we became aware of the gcc optimizer bug.) The BSD TAILQ macros are generally considered to be safer than the CIRCLEQ macros, and the various open-source BSD derivatives have made the corresponding change to their libdb sources years ago, with no reported ill effects that I can see. Original report from Ben Kaduk: == In some conditions, propagating a kerberos database to a slave KDC server can stall. This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros, apparently due to overzealous strict aliasing deductions. One case of this stall is reported at http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html (and the rest of the thread), and there is an entry in the upstream bugtracker at http://krbdev.mit.edu/rt/Ticket/Display.html?id=7860 . gcc 4.9 (as used in Debian unstable at present) is not believed to induce this problem. Upstream has patched their code to use the TAILQ family of macros instead, as a workaround, but that workaround has not yet appeared in an upstream release: https://github.com/krb5/krb5/commit/26d8744129 Because of the different compiler versions used on Debian and
[Touch-packages] [Bug 1361940] Re: patches for cgo on arm64
** Branch linked: lp:debian/gnat-4.9 -- 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/1361940 Title: patches for cgo on arm64 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: New Status in “gcc-4.9” source package in Utopic: Fix Released Status in “gccgo-4.9” source package in Utopic: Invalid Bug description: Hi, I'm attaching three patches that together with https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1361946 makes cgo work with gccgo on arm64. 0001-compiler-symbol-names-should-have-.-replaced-with-_.patch -- this isn't actually arm64 specific at all, but a general gccgo/cgo problem 0002-debug-elf-support-arm64-relocations.patch -- cgo parses dwarf data from .o files and can't do it without this 0003-Enable-cgo-by-default-on-linux-arm64.patch -- this means that I don't have to remember to run export CGO_ENABLED=1 all the time Let me know if you need any more info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.9/+bug/1361940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp