[Touch-packages] [Bug 1380014] [NEW] modemmanager should blacklist Freetronics devices
Public bug reported:
In a similar vein to Bug #910736, there are more Arduino related devices
that must be blacklisted.
For the LeoStick, the following is required:
-- /etc/udev/rules.d/77-modem-manager-freetronics.rules
--
ATTRS{idVendor}==26ba, ENV{ID_MM_DEVICE_IGNORE}=1
ATTRS{idVendor}==20a0, ENV{ID_MM_DEVICE_IGNORE}=1
---
See http://www.freetronics.com/pages/leostick-getting-started-guide in the
section Problems Uploading on Linux.
There are also some additional devices listed on the end of Bug #910736
after it was marked as FixedReleased.
** Affects: modemmanager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1380014
Title:
modemmanager should blacklist Freetronics devices
Status in “modemmanager” package in Ubuntu:
New
Bug description:
In a similar vein to Bug #910736, there are more Arduino related
devices that must be blacklisted.
For the LeoStick, the following is required:
-- /etc/udev/rules.d/77-modem-manager-freetronics.rules
--
ATTRS{idVendor}==26ba, ENV{ID_MM_DEVICE_IGNORE}=1
ATTRS{idVendor}==20a0, ENV{ID_MM_DEVICE_IGNORE}=1
---
See http://www.freetronics.com/pages/leostick-getting-started-guide in the
section Problems Uploading on Linux.
There are also some additional devices listed on the end of Bug
#910736 after it was marked as FixedReleased.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1380014/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059872] Re: Error formatting disk using disk utility
Fresh Ubuntu 14.04.1 LTS. Disk utility fails in formatting empty partition on usb-disk: Error formatting partition Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1059872 Title: Error formatting disk using disk utility Status in “udisks2” package in Ubuntu: Invalid Status in “util-linux” package in Ubuntu: Fix Released Status in “udisks2” source package in Trusty: Invalid Status in “util-linux” source package in Trusty: Triaged Status in “util-linux” package in Debian: Fix Released Bug description: Formatting a SD card using the disk utility fails with an error message Error formatting disk - Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0) Steps to repro: Launch the disk utility Plug a SD card into the computer Select the SD card and click on the gears icon at the top right of the application From the drop down menu, select Format Disk maintain the default setting and select Format Acknowledge warnings After format process has been going for a while, the error message shown above pops up Workaround: After selecting the SD card, instead of clicking the gear icon to format, click the partition in the Volumes section. Delete the partition (minus icon) Create a new partition - The underlying problem is that the wipefs tool from util-linux does not work any more. === TEST CASE === $ sudo modprobe scsi_debug dev_size_mb=200 # this creates a new /dev/sdX, usually /dev/sdb; check dmesg! # now create a partition table $ cat EOF | sudo sfdisk /dev/sdb # partition table of /dev/sdb unit: sectors /dev/sdb1 : start= 32, size= 409568, Id=83 /dev/sdb2 : start=0, size=0, Id= 0 /dev/sdb3 : start=0, size=0, Id= 0 /dev/sdb4 : start=0, size=0, Id= 0 EOF # now create an ext4 file system: $ sudo mkfs.ext4 /dev/sdb1 # check contents: $ sudo blkid -p /dev/sdb /dev/sdb1 /dev/sdb: PTTYPE=dos /dev/sdb1: UUID=4bd1c542-a61f-43c4-a7e5-cc50e66e6b5a VERSION=1.0 TYPE=ext4 USAGE=filesystem PART_ENTRY_SCHEME=dos PART_ENTRY_TYPE=0x83 PART_ENTRY_NUMBER=1 PART_ENTRY_OFFSET=32 PART_ENTRY_SIZE=409568 PART_ENTRY_DISK=8:16 # wipe: $ sudo wipefs -a /dev/sdb # now check contents again $ sudo blkid -p /dev/sdb /dev/sdb1 # in the broken case, you will still see a dos partition table and the ext4 partition; in the working case, /dev/sdb won't show anything and /dev/sdb1 does not exist any more ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: udisks 1.0.4-6 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CustomUdevRuleFiles: 51-android.rules 51-android.rules~ Date: Mon Oct 1 15:07:46 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120720.1) MachineType: FOXCONN NT-A2400NT-A3500 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=fcc445e4-9662-47cc-855d-ca17ad1c2a87 ro quiet splash vt.handoff=7 SourcePackage: udisks UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd03/29/2011:svnFOXCONN:pnNT-A2400NT-A3500:pvrFAB1.0:rvnFOXCONN:rnNT-A2400NT-A3500:rvrFAB1.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400NT-A3500 dmi.product.version: FAB 1.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1059872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379448] Re: Can't install or update apps on Ubuntu Touch
Seems like after removing the Ubuntu One account and adding it back everything works -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1379448 Title: Can't install or update apps on Ubuntu Touch Status in “click” package in Ubuntu: Incomplete Bug description: Apparently there are network errors (even though network works fine), so the log says WARNING - Error received from UDM during startDownload: Network Error. When hitting the close button for the download error, more errors appear in the log: click_query_error-quark failed to canonicalize (appid here). I'm on r243. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1379448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380044] [NEW] Welcome screen should be visible immediately when screen is activated
Public bug reported: When locking my device with the power button, and then activating it, I briefly see the previously-surfaced application before the welcome screen is drawn over that. What should happen is that activating the screen shows the welcome screen instantly. I suspect we need to draw the welcome screen when then button is pressed, and fade-out the screen to black. This way, the welcome screen is already in place when we turn the screen on again. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1380044 Title: Welcome screen should be visible immediately when screen is activated Status in “unity8” package in Ubuntu: New Bug description: When locking my device with the power button, and then activating it, I briefly see the previously-surfaced application before the welcome screen is drawn over that. What should happen is that activating the screen shows the welcome screen instantly. I suspect we need to draw the welcome screen when then button is pressed, and fade-out the screen to black. This way, the welcome screen is already in place when we turn the screen on again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380044/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379448] Re: Can't install or update apps on Ubuntu Touch
** Changed in: click (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1379448 Title: Can't install or update apps on Ubuntu Touch Status in “click” package in Ubuntu: New Bug description: Apparently there are network errors (even though network works fine), so the log says WARNING - Error received from UDM during startDownload: Network Error. When hitting the close button for the download error, more errors appear in the log: click_query_error-quark failed to canonicalize (appid here). I'm on r243. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1379448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379021] Re: after utopic upgrade: boot delays for 2 minutes
Strangely, after purging teh configs of my removed packages (that still had upstart jobs on my machine) I did nto have to wait 2 mins for network while my machine booted this morning. I am hoping that this fixed state keeps repeating. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1379021 Title: after utopic upgrade: boot delays for 2 minutes Status in “upstart” package in Ubuntu: Confirmed Bug description: After upgrading to utopic, my system waits 2 minutes for network at boot, the boots ok. This has happened in previous releases as well for other people and is an annoying issue which will alarm many people especially the non-techinical users. Also, many fixes described in older bug reports no longer apply as ubuntu does not need them yet the bug is still alive and kicking. --- ApportVersion: 2.14.7-0ubuntu5 Architecture: i386 CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2011-11-11 (1062 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.17.0-rc7-custom root=UUID=239a7bf6-c6d6-468d-90fb-5705e76c8def ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M Tags: utopic Uname: Linux 3.17.0-rc7-custom i686 UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) UserGroups: adm admin audio cdrom dialout fuse lp lpadmin netdev plugdev powerdev sambashare sbuild scanner vboxusers video _MarkForUpload: True modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: u'/etc/at.deny'] modified.conffile..etc.bluetooth.audio.conf: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.default.jenkins: [modified] modified.conffile..etc.init.jenkins.conf: [modified] modified.conffile..etc.init.runsvdir.conf: [modified] modified.conffile..etc.vsftpd.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-08-07T17:00:01.738247 mtime.conffile..etc.bluetooth.audio.conf: 2014-07-08T18:53:12.563803 mtime.conffile..etc.default.cups: 2014-04-10T18:37:14.830556 mtime.conffile..etc.default.jenkins: 2012-11-03T21:42:41.983374 mtime.conffile..etc.init.jenkins.conf: 2013-09-13T16:17:44.852882 mtime.conffile..etc.init.runsvdir.conf: 2011-03-17T16:02:21 mtime.conffile..etc.vsftpd.conf: 2012-07-07T13:06:07.102856 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1379021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296487] Re: Initial zoom level is slightly under 100%
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in Eye of GNOME: New Status in “eog” package in Ubuntu: Confirmed Status in “ubuntu-themes” package in Ubuntu: Confirmed Bug description: When opening an image, the zoom level is displayed as 100%, but the image is visibly blurry from being slightly zoomed out. There are a few pixels of black bar on the right and left edges of the image. Expanding the window vertically lets the image display at 1:1 zoom. This occurs with images that should be small enough to be displayed at 100% zoom. For example: a 960x540 image on a 1920x1080 display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 18:06:29 2014 InstallationDate: Installed on 2014-02-16 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1296487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296487] Re: Initial zoom level is slightly under 100%
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in Eye of GNOME: New Status in “eog” package in Ubuntu: Confirmed Status in “ubuntu-themes” package in Ubuntu: Confirmed Bug description: When opening an image, the zoom level is displayed as 100%, but the image is visibly blurry from being slightly zoomed out. There are a few pixels of black bar on the right and left edges of the image. Expanding the window vertically lets the image display at 1:1 zoom. This occurs with images that should be small enough to be displayed at 100% zoom. For example: a 960x540 image on a 1920x1080 display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 18:06:29 2014 InstallationDate: Installed on 2014-02-16 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1296487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296487] Re: Initial zoom level is slightly under 100%
** Package changed: light-themes (Ubuntu) = ubuntu-themes (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1296487 Title: Initial zoom level is slightly under 100% Status in Eye of GNOME: New Status in “eog” package in Ubuntu: Confirmed Status in “ubuntu-themes” package in Ubuntu: Confirmed Bug description: When opening an image, the zoom level is displayed as 100%, but the image is visibly blurry from being slightly zoomed out. There are a few pixels of black bar on the right and left edges of the image. Expanding the window vertically lets the image display at 1:1 zoom. This occurs with images that should be small enough to be displayed at 100% zoom. For example: a 960x540 image on a 1920x1080 display. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eog 3.10.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 23 18:06:29 2014 InstallationDate: Installed on 2014-02-16 (35 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1296487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874283]
And may be related or duplicate of this as well: https://bugs.freedesktop.org/show_bug.cgi?id=39931 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/874283 Title: Empathy IM Client does not connect to Zimbra via XMPP Status in Jabber/XMPP connection manager: Incomplete Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: This is the error from the debug log: on_connection_ready: got error: WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error: -12: GNUTLS_E_FATAL_ALERT_RECEIVED ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 16:31:45 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:cs_CZ:cs:en PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874283]
Issue still present using Ubuntu 14.04. While this may be related to a wrong behaviour from the server side it works flawlessly using pidgin. Related launchpad bug: https://bugs.launchpad.net/ubuntu/+source /telepathy-gabble/+bug/874283 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/874283 Title: Empathy IM Client does not connect to Zimbra via XMPP Status in Jabber/XMPP connection manager: Incomplete Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: This is the error from the debug log: on_connection_ready: got error: WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error: -12: GNUTLS_E_FATAL_ALERT_RECEIVED ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 16:31:45 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:cs_CZ:cs:en PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 874283] Re: Empathy IM Client does not connect to Zimbra via XMPP
** Bug watch added: freedesktop.org Bugzilla #39931 https://bugs.freedesktop.org/show_bug.cgi?id=39931 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/874283 Title: Empathy IM Client does not connect to Zimbra via XMPP Status in Jabber/XMPP connection manager: Incomplete Status in “telepathy-gabble” package in Ubuntu: Triaged Bug description: This is the error from the debug log: on_connection_ready: got error: WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): SSL handshake error: -12: GNUTLS_E_FATAL_ALERT_RECEIVED ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 16:31:45 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: LANGUAGE=en_GB:cs_CZ:cs:en PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-gabble/+bug/874283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380050] [NEW] Ubuntu boots to a black screen
Public bug reported: Ubuntu boots to a black screen. I can hear the opening chimes, but I cannot see anything until I switch my screen off and on again. Then I can see the login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Oct 11 12:49:21 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1041] InstallationDate: Installed on 2014-09-26 (14 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: HP-Pavilion KA869AA-ABZ a6335.it ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-36-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.13 dmi.board.name: NARRA2 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 2.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.13:bd10/29/2007:svnHP-Pavilion:pnKA869AA-ABZa6335.it:pvr:rvnASUSTekComputerINC.:rnNARRA2:rvr2.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: KA869AA-ABZ a6335.it dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.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: Sat Oct 11 12:48:11 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMLK Trust Keyboard 14909 KEYBOARD, id 8 inputMLK Trust Keyboard 14909 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1380050 Title: Ubuntu boots to a black screen Status in “xorg” package in Ubuntu: New Bug description: Ubuntu boots to a black screen. I can hear the opening chimes, but I cannot see anything until I switch my screen off and on again. Then I can see the login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Oct 11 12:49:21 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1041] InstallationDate: Installed on 2014-09-26 (14 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: HP-Pavilion KA869AA-ABZ a6335.it ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-36-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.13 dmi.board.name: NARRA2
[Touch-packages] [Bug 1380084] [NEW] SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Public bug reported: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 Status in “openssh” package in Ubuntu: New Bug description: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with apparmor 3.0 RC1 kernel
Yep, Docker works again with kernel 3.16.0-22.29. Thanks for fixing this so promptly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with apparmor 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: Invalid Status in “docker.io” package in Ubuntu: Invalid Status in “linux” package in Ubuntu: Fix Released Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. FYI, 3.16.0-17.23 is in utopic-proposed now and on its way to utopic, which will affect docker.io in Ubuntu. Workaround until this bug is fixed is to boot into 3.16.0-16.22 or earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380100] [NEW] Screen should darken as launcher is revealed
Public bug reported: When the left edge launcher is revealed over an app or a scope other than the apps scope, the app should darken smoothly and proportionately to the revealing movement of the launcher. At the moment, the screen darkens after the launcher is fully committed. Instead the degree of darkening of the screen should be correlated to the extent of the launcher reveal. As the launcher is hinted, the screen should darken a little, and as it is revealed the rest of the darkening should happen, till the commit at which point the app / screen is at the final level of darkening. If the left edge swipe continues then we expect to reveal the app scope, which would be undimmed and hence contrast strongly with the app (or other scope) that was visible. This will serve to strengthen the hint / reveal of the launcher, and also to highlight the emergence of the app scope. It also matches the immediate dimming of the screen during a right-edge swipe. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1380100 Title: Screen should darken as launcher is revealed Status in “unity8” package in Ubuntu: New Bug description: When the left edge launcher is revealed over an app or a scope other than the apps scope, the app should darken smoothly and proportionately to the revealing movement of the launcher. At the moment, the screen darkens after the launcher is fully committed. Instead the degree of darkening of the screen should be correlated to the extent of the launcher reveal. As the launcher is hinted, the screen should darken a little, and as it is revealed the rest of the darkening should happen, till the commit at which point the app / screen is at the final level of darkening. If the left edge swipe continues then we expect to reveal the app scope, which would be undimmed and hence contrast strongly with the app (or other scope) that was visible. This will serve to strengthen the hint / reveal of the launcher, and also to highlight the emergence of the app scope. It also matches the immediate dimming of the screen during a right-edge swipe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380110] [NEW] comments inside parentheses mess up the syntax coloring of shell script
Public bug reported: Hi, I've found the following bug with syntax coloring of shell scripts in vi and vim. If you add comments outside parenthesis, it works fine. But if you add comments inside parenthesis, or worse comments with quotes, the syntax coloring is totally messed up. I join a sample shell script to demonstrate the bug. Best regards, Laurent Lyaudet ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Attachment added: sample script to reproduce the bug https://bugs.launchpad.net/bugs/1380110/+attachment/4231654/+files/testBugVim.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1380110 Title: comments inside parentheses mess up the syntax coloring of shell script Status in “vim” package in Ubuntu: New Bug description: Hi, I've found the following bug with syntax coloring of shell scripts in vi and vim. If you add comments outside parenthesis, it works fine. But if you add comments inside parenthesis, or worse comments with quotes, the syntax coloring is totally messed up. I join a sample shell script to demonstrate the bug. Best regards, Laurent Lyaudet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1380110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] [NEW] Manage Scopes - All Is Unusable
Public bug reported: This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture ** Affects: unity8 (Ubuntu) Importance: Critical Status: Confirmed ** Tags: avengers rtm14 ** Attachment added: broken manage scopes UI https://bugs.launchpad.net/bugs/1380120/+attachment/4231688/+files/manage-scopes.png -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Confirmed Bug description: This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] Re: Manage Scopes - Is Unusable
i see the same issue. ** Changed in: unity8 (Ubuntu) Status: New = Confirmed ** Changed in: unity8 (Ubuntu) Importance: Undecided = Critical ** Tags added: rtm14 ** Description changed: - This is in krillin r99. + This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Confirmed Bug description: This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] Re: Manage Scopes - All Is Unusable
** Summary changed: - Manage Scopes - Is Unusable + Manage Scopes - All Is Unusable -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Confirmed Bug description: This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376530] Re: GTK apps crashing with Attempt to unlock mutex that was not locked
** Changed in: gtk+2.0 (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1376530 Title: GTK apps crashing with Attempt to unlock mutex that was not locked Status in “gtk+2.0” package in Ubuntu: Fix Released Status in “gtk+2.0” package in Debian: Fix Released Bug description: Attempting to run some GTK apps (e.g. pyrenamer) on 14.10 results in an immediate crash, with the message Attempt to unlock mutex that was not locked. https://bugzilla.gnome.org/show_bug.cgi?id=735428 seems to be the relevant upstream bug, and there is a patch here: https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec To some extent, this seems to be the result of individual projects using GTK incorrectly, and some fixes have been made to those individual projects. *However*, I am also seeing this bug occur in a closed source third party application, Stata 13. As Emmanuele Bassi mentions in the Gnome bug thread, there are probably a lot of applications out in the wild affected by the same issue, that in some cases cannot be fixed, so it would be good if a fix could be included in the versions of GTK that Ubuntu ships. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgtk-3-0 3.12.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 2 10:05:20 2014 InstallationDate: Installed on 2014-04-24 (160 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: gtk+3.0 UpgradeStatus: Upgraded to utopic on 2014-10-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1376530/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] Re: Manage Scopes - All Is Unusable
also on mako -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Confirmed Bug description: This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268146] Re: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe)
Running Ubuntu 14.04 on Toshiba Satellite E45-B4200. The solution #21 did not work for me. The CPU still have a constant high of consume (+- 30% strangely only for CPU1) without any programs opened. I tried with other Ubuntu variants like Lubuntu or Xubuntu and the problem still remains. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1268146 Title: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe) Status in “mesa” package in Ubuntu: Confirmed Bug description: I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from compiz. Strangely, glxinfo reports this, which is totally incorrect - I'm running on Intel Sandy Bridge HD3000 graphics and VMware isn't even installed on this PC: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.0.1 So I guess that compiz might be using lots of cpu because it's using llvmpipe as the renderer. So is this a mesa bug? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Jan 11 22:27:28 2014 DistUpgraded: 2014-01-11 12:30:22,360 ERROR SystemError from cache.commit(): installArchives() failed DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:050e] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-25 (504 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro quiet splash intel_pstate=enable crashkernel=384M-:128M vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sat Jan 11 22:20:55 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41063 vendor DEL xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1268146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268146] Re: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe)
Running Ubuntu 14.04 on Toshiba Satellite E45-B4200. The solution #21 did not work for me. The CPU still have a high constant of consume value (+- 30% strangely only for CPU-1) with no programs opened. I tried with other Ubuntu variants like Lubuntu or Xubuntu and problem still remains. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1268146 Title: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe) Status in “mesa” package in Ubuntu: Confirmed Bug description: I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from compiz. Strangely, glxinfo reports this, which is totally incorrect - I'm running on Intel Sandy Bridge HD3000 graphics and VMware isn't even installed on this PC: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.0.1 So I guess that compiz might be using lots of cpu because it's using llvmpipe as the renderer. So is this a mesa bug? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Jan 11 22:27:28 2014 DistUpgraded: 2014-01-11 12:30:22,360 ERROR SystemError from cache.commit(): installArchives() failed DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:050e] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-25 (504 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro quiet splash intel_pstate=enable crashkernel=384M-:128M vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sat Jan 11 22:20:55 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41063 vendor DEL xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1268146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380129] [NEW] No mimetype listed for .ttf files
Public bug reported: Ideally they would be listed, with a mimetype of application/x-font- ttf ** Affects: mime-support (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1380129 Title: No mimetype listed for .ttf files Status in “mime-support” package in Ubuntu: New Bug description: Ideally they would be listed, with a mimetype of application/x-font- ttf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1380129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376495] Re: autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes camera-app
I believe this is just a crash with the test. Cannot be reproduced by hand. @kaleo please take over this branch from omer which seems to fix the broken test (and a few others) https://code.launchpad.net/~canonical-platform-qa/camera-app/lp1366825_fix_zoom/+merge/233725 And lets land these test fixes and this problem should go away. Of course first look at the crash and make sure it's not an actual problem with the underlying code. ** Changed in: camera-app (Ubuntu) Assignee: Ugo Riboni (uriboni) = Florian Boucault (fboucault) ** Changed in: camera-app Assignee: Ugo Riboni (uriboni) = Florian Boucault (fboucault) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1376495 Title: autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes camera-app Status in Camera App: Confirmed Status in “camera-app” package in Ubuntu: Confirmed Bug description: Summary: autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out crashes camera-app steps: 1. phablet-click-test-setup -s $ANDROID_SERIAL 2. phablet-config -s $ANDROID_SERIAL autopilot --dbus-probe enable 3. adb -s $ANDROID_SERIAL shell 4. cd autopilot 5. autopilot3 run camera_app.tests.test_zoom.TestCameraZoom.test_slider_zoom_out - 6. ls /var/crash expected results: test passes without crashing camera app actual results: test crashes camera app base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/devel-proposed device: mako build_number: 263 channel_target: ubuntu-touch/utopic-proposed version_detail: ubuntu=20140930,device=20140929.1,custom=mako-0.6,version=263 com.ubuntu.camera 3.0.0.387 To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1376495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380129] Re: No mimetype listed for .ttf files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mime-support (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1380129 Title: No mimetype listed for .ttf files Status in “mime-support” package in Ubuntu: Confirmed Bug description: Ideally they would be listed, with a mimetype of application/x-font- ttf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1380129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380133] [NEW] [regression] horizontal-list not displaying properly in scopes
Public bug reported: build r99 Krillin How to reproduce: open NearBy scope or Music scope or News scope.. the first item should be a horizontal list of cards. but nothing is displayed See attached pic. ** Affects: unity8 (Ubuntu) Importance: Critical Status: New ** Tags: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1380133 Title: [regression] horizontal-list not displaying properly in scopes Status in “unity8” package in Ubuntu: New Bug description: build r99 Krillin How to reproduce: open NearBy scope or Music scope or News scope.. the first item should be a horizontal list of cards. but nothing is displayed See attached pic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380133] Re: [regression] horizontal-list not displaying properly in scopes
** Attachment added: regression-hl.png https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380133/+attachment/4231704/+files/regression-hl.png -- 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/1380133 Title: [regression] horizontal-list not displaying properly in scopes Status in “unity8” package in Ubuntu: New Bug description: build r99 Krillin How to reproduce: open NearBy scope or Music scope or News scope.. the first item should be a horizontal list of cards. but nothing is displayed See attached pic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1214352]
(In reply to Björn Michaelsen from comment #68) Scoping this bug clearly only on the missing deps for KDE thanks to the excellent summary in comment 59. ...which has become moot with http://cgit.freedesktop.org/libreoffice/core/commit/?id=f9f9aa9873c5851da86d33ca75e937ac022206a3 Remove smb from X-KDE-Protocols lines, see http://lists.freedesktop.org/archives/libreoffice/2014-October/063904.html Re: X-KDE-Protocols=...,smb,... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The G Library - GLib: Fix Released Status in “glib2.0” package in Ubuntu: Confirmed Bug description: On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1214352] Re: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses
** Changed in: df-libreoffice Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Fix Released Status in The G Library - GLib: Fix Released Status in “glib2.0” package in Ubuntu: Confirmed Bug description: On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380148] [NEW] package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: tried to update the system after a long time (7 months) and update failed showing this error. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: tzdata 2014e-0ubuntu0.12.04 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sat Oct 11 18:46:10 2014 DuplicateSignature: package:tzdata:2014e-0ubuntu0.12.04:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MarkForUpload: True PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to precise on 2012-08-06 (796 days ago) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check precise -- 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/1380148 Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in “tzdata” package in Ubuntu: New Bug description: tried to update the system after a long time (7 months) and update failed showing this error. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: tzdata 2014e-0ubuntu0.12.04 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sat Oct 11 18:46:10 2014 DuplicateSignature: package:tzdata:2014e-0ubuntu0.12.04:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MarkForUpload: True PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to precise on 2012-08-06 (796 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1380148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] Re: Manage Scopes - All Is Unusable
You guys have some special phones, I totally can't reproduce this :/ Tried on both krillin (rtm-proposed an devel-proposed) and mako (rtm- proposed), everything behaves fine... And this wouldn't have gotten through ours *and* QA's testing if it was common. Is this constant for you? Are there any steps you're taking that lead to this? :| ** Changed in: unity8 (Ubuntu) Status: Confirmed = Incomplete -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Incomplete Bug description: This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380133] Re: [regression] horizontal-list not displaying properly in scopes
You guys have some special phones, I totally can't reproduce this :/ Tried on both krillin (rtm-proposed an devel-proposed) and mako (rtm- proposed), everything behaves fine... And this wouldn't have gotten through ours *and* QA's testing if it was common. Is this constant for you? Are there any steps you're taking that lead to this? :| ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- 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/1380133 Title: [regression] horizontal-list not displaying properly in scopes Status in “unity8” package in Ubuntu: Incomplete Bug description: build r99 Krillin How to reproduce: open NearBy scope or Music scope or News scope.. the first item should be a horizontal list of cards. but nothing is displayed See attached pic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380148] Re: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Tags removed: need-duplicate-check -- 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/1380148 Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in “tzdata” package in Ubuntu: New Bug description: tried to update the system after a long time (7 months) and update failed showing this error. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: tzdata 2014e-0ubuntu0.12.04 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sat Oct 11 18:46:10 2014 DuplicateSignature: package:tzdata:2014e-0ubuntu0.12.04:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MarkForUpload: True PackageArchitecture: all SourcePackage: tzdata Title: package tzdata 2014e-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to precise on 2012-08-06 (796 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1380148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380083] Re: Vim command mode abreviations and insert mode maps are broken
** Description changed: 1) lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 2) apt-cache policy vim-gtk vim-gtk: - Installed: 2:7.4.052-1ubuntu3 - Candidate: 2:7.4.052-1ubuntu3 - Version table: - *** 2:7.4.052-1ubuntu3 0 - 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2:7.4.052-1ubuntu3 + Candidate: 2:7.4.052-1ubuntu3 + Version table: + *** 2:7.4.052-1ubuntu3 0 + 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages + 100 /var/lib/dpkg/status 3) In your .vimrc or in a vim editing session, try adding the following: cab Q q - inoremap C-z C-guC-u - The first should make (and does in non-14.04 versions of vim) the typo command ':Q' work like the intended ':q'. - The second should create a CTRL-z alias for undo while in insert mode. + This should make (and does in non-14.04 versions of vim) the typo + command ':Q' work like the intended ':q'. - 4) Neither work. I have many other cab and imap statements in my .vimrc, - it's not specific to these examples. Only normal mode maps work. + 4) I have many other cab statements in my .vimrc, it's not specific to + this example. Normal and Insert mode maps work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1380083 Title: Vim command mode abreviations and insert mode maps are broken Status in “vim” package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 2) apt-cache policy vim-gtk vim-gtk: Installed: 2:7.4.052-1ubuntu3 Candidate: 2:7.4.052-1ubuntu3 Version table: *** 2:7.4.052-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status 3) In your .vimrc or in a vim editing session, try adding the following: cab Q q This should make (and does in non-14.04 versions of vim) the typo command ':Q' work like the intended ':q'. 4) I have many other cab statements in my .vimrc, it's not specific to this example. Normal and Insert mode maps work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1380083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332210] Re: Apple Magic Mouse battery life read as 0%
** This bug is no longer a duplicate of bug 1318026 05ac:8286 [MacBookPro10,1] mouse battery indicator shows 0% -- 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/1332210 Title: Apple Magic Mouse battery life read as 0% Status in “upower” package in Ubuntu: Confirmed Bug description: Despite being fully-functional, my Apple Magic Mouse is shown to be in the discharging state at 0%. It is also marked rechargable, which is false -- you need to replace the batteries when they run out. Output of `upower --dump` attached. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 19 10:30:37 2014 InstallationDate: Installed on 2014-04-01 (79 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: upower UpgradeStatus: Upgraded to trusty on 2014-04-24 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1332210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop
This appeared for me after upgrading from 13.04 to 14.04. After boot, the keyboard layout seems English although Danish is my only installed layout. -- 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/1240198 Title: Wrong keyboard layout active after booting into desktop Status in “ibus” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=de XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377812] Re: Pull down indicator menu not working properly
I cannot rule out that this is a hardware issue. Following the no go mako-rtm #82 I flashed my phone back to Android, before putting UT back again. In the short while I was on Android I experienced a somewhat strange behaviour with the pull down menu there too... -- 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/1377812 Title: Pull down indicator menu not working properly Status in “unity8” package in Ubuntu: Incomplete Bug description: Mako rtm r72 I am not sure where to post this bug, so I post it here. Feel free to move it elsewhere if this is not the correct place to post it. In the last two images for mako (171 172) it is not working properly. Either I can't pull the menu down more than 10-15 mm or it flickers while being pulled down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301224] Re: aa-genprof crashed with TypeError in parse_profile_data(): 'bool' object does not support item assignment
This looks like a duplicate of the (already fixed) bug 1319829. Can you reproduce this bug with a newer AppArmor version? Please test at least with 2.8.96 aka 2.9 beta2, testing with beta3 would be even better. ** Changed in: apparmor Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1301224 Title: aa-genprof crashed with TypeError in parse_profile_data(): 'bool' object does not support item assignment Status in AppArmor Linux application security framework: Incomplete Status in “apparmor” package in Ubuntu: New Bug description: Installed apparmor-profiles, apparmor-utils, apparmor-notify packages and rebooted then this crash happened on start-up. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: apparmor-utils 2.8.95~2430-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 Date: Tue Apr 1 20:46:29 2014 ExecutablePath: /usr/sbin/aa-genprof InstallationDate: Installed on 2014-03-24 (9 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64+mac (20131016.1) InterpreterPath: /usr/bin/python3.4 ProcCmdline: /usr/bin/python3 /usr/sbin/aa-genprof feh ProcKernelCmdline: BOOT_IMAGE=/efi/ubuntu/vmlinuz-3.13.0-20-generic root=/dev/mapper/vg-root0 ro quiet splash PythonArgs: ['/usr/sbin/aa-genprof', 'feh'] SourcePackage: apparmor Syslog: Apr 2 10:07:24 PC dbus[613]: [system] AppArmor D-Bus mediation is enabled Title: aa-genprof crashed with TypeError in parse_profile_data(): 'bool' object does not support item assignment UpgradeStatus: Upgraded to trusty on 2014-03-29 (3 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1301224/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] Re: Manage Scopes - All Is Unusable
I updated to #99 rtm-proposed,rebooted and cannot reproduce. I'll play with it a bit more, spec. re adding / removing scopes and will report if I can reproduce -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Incomplete Bug description: This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] Re: Manage Scopes - All Is Unusable
I have done a lot of favoriting and unfavoritng of scopes. That's the only thing that I can think of that would be at all relevant. -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Incomplete Bug description: This is in krillin r99 rtm-proposed Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 316042] Re: Adding MinorFS package to ubuntu.
Maybe Jamie was confused by the perl keyword in the description... That said - Nobody stops you from reopening a bug ;-) - and to make things easier, I just did that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/316042 Title: Adding MinorFS package to ubuntu. Status in “apparmor” package in Ubuntu: Won't Fix Bug description: Binary package hint: apparmor MinorFs is a (capability based) discretionary access control extension to AppArmor implemented as a set of cooperating userspace (fuse) filesystems. The latest version (0.3.5) has a howto as to installation on ubuntu 8.10. MinorFs depends on a few cpan perl modules not currently packaged for ubuntu. I'm not sure if this is the right channel, but I (as the minorfs author) would like to work with an experienced ubuntu package maintainer on getting and keeping MinorFs packaged for ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/316042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 316042] Re: Adding MinorFS package to ubuntu.
Argh - at least that was the plan. It seems I don't have the permissions to reopen the bug, so please do it yourself or poke Jamie ;-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/316042 Title: Adding MinorFS package to ubuntu. Status in “apparmor” package in Ubuntu: Won't Fix Bug description: Binary package hint: apparmor MinorFs is a (capability based) discretionary access control extension to AppArmor implemented as a set of cooperating userspace (fuse) filesystems. The latest version (0.3.5) has a howto as to installation on ubuntu 8.10. MinorFs depends on a few cpan perl modules not currently packaged for ubuntu. I'm not sure if this is the right channel, but I (as the minorfs author) would like to work with an experienced ubuntu package maintainer on getting and keeping MinorFs packaged for ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/316042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380133] Re: [regression] horizontal-list not displaying properly in scopes
I am with Saviq, can't reproduce on #99 -- 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/1380133 Title: [regression] horizontal-list not displaying properly in scopes Status in “unity8” package in Ubuntu: Incomplete Bug description: build r99 Krillin How to reproduce: open NearBy scope or Music scope or News scope.. the first item should be a horizontal list of cards. but nothing is displayed See attached pic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1298678] Re: Python utils lack support for pivot_root rules
This bug is fixed (just tested with current bzr) - looks like nobody
closed it ;-)
** Changed in: apparmor
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1298678
Title:
Python utils lack support for pivot_root rules
Status in AppArmor Linux application security framework:
Fix Committed
Status in “apparmor” package in Ubuntu:
Fix Released
Bug description:
aa.py doesn't support pivot_root rules and emits a traceback when
encountering them:
$ mkdir /tmp/profs
$ printf profile pr {\n pivot_root /other,\n } /tmp/profs/pr
$ sudo aa-enforce -d /tmp/profs /tmp/profs/pr
Traceback (most recent call last):
File /usr/sbin/aa-enforce, line 30, in module
tool.cmd_enforce()
File /usr/lib/python3/dist-packages/apparmor/tools.py, line 153, in
cmd_enforce
apparmor.read_profiles()
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 2564, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 2590, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 3063, in
parse_profile_data
raise AppArmorException(_('Syntax Error: Unknown line found in file: %s
line: %s') % (file, lineno + 1))
apparmor.common.AppArmorException: 'Syntax Error: Unknown line found in file:
/tmp/profs/pr line: 2'
Error in sys.excepthook:
Traceback (most recent call last):
File /usr/lib/python3/dist-packages/apport_python_hook.py, line 103, in
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File /usr/lib/python3/dist-packages/apport/report.py, line 546, in
add_proc_info
ret = self.get_logind_session(pid)
File /usr/lib/python3/dist-packages/apport/report.py, line 1593, in
get_logind_session
if len(my_cgroup) 2:
UnboundLocalError: local variable 'my_cgroup' referenced before assignment
Original exception was:
Traceback (most recent call last):
File /usr/sbin/aa-enforce, line 30, in module
tool.cmd_enforce()
File /usr/lib/python3/dist-packages/apparmor/tools.py, line 153, in
cmd_enforce
apparmor.read_profiles()
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 2564, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 2590, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File /usr/lib/python3/dist-packages/apparmor/aa.py, line 3063, in
parse_profile_data
raise AppArmorException(_('Syntax Error: Unknown line found in file: %s
line: %s') % (file, lineno + 1))
apparmor.common.AppArmorException: 'Syntax Error: Unknown line found in file:
/tmp/profs/pr line: 2'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1298678/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1249438] Re: Opening a tel:// link doesn't open dialer-app
Actually also mailto : URL: mailto:u...@example.com This behaviour is consistent with how the Web browser refuses to handle unsupported media types, e.g. image/tiff: nothing happens when you press and a new tab comes blank. Is this by design? It does not look like a good one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1249438 Title: Opening a tel:// link doesn't open dialer-app Status in Web Browser App: Confirmed Status in “webbrowser-app” package in Ubuntu: Confirmed Bug description: When clicking a link to tel://blah, the browser says it doesn't know how to handle the link, rather than opening the dialer-app. Steps to reproduce: 1) Open browser 2) Search for a business on Google 3) Click the Call result 4) Note the dialer-app is not opened Expected results: Dialer is opened to the provided number Actual results: Browser tries to open link, fails ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: webbrowser-app (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 8 12:39:45 2013 InstallationDate: Installed on 2013-04-26 (196 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: webbrowser-app UpgradeStatus: Upgraded to saucy on 2013-08-13 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1249438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1249438] Re: Opening a tel:// link doesn't open dialer-app
Oops, my bad: the mailto URL shows the Network Error screen, and so does URL: news:news.answers . The message in the Network Error screen is bogus; no amount of refreshing will ever fix the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1249438 Title: Opening a tel:// link doesn't open dialer-app Status in Web Browser App: Confirmed Status in “webbrowser-app” package in Ubuntu: Confirmed Bug description: When clicking a link to tel://blah, the browser says it doesn't know how to handle the link, rather than opening the dialer-app. Steps to reproduce: 1) Open browser 2) Search for a business on Google 3) Click the Call result 4) Note the dialer-app is not opened Expected results: Dialer is opened to the provided number Actual results: Browser tries to open link, fails ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: webbrowser-app (not installed) ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 8 12:39:45 2013 InstallationDate: Installed on 2013-04-26 (196 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: webbrowser-app UpgradeStatus: Upgraded to saucy on 2013-08-13 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1249438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380083] Re: Vim command mode abreviations and insert mode maps are broken
Close please. This was a side-effect of ':set paste', the systems where it was workings didn't have the newest version of my '.vimrc'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1380083 Title: Vim command mode abreviations and insert mode maps are broken Status in “vim” package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 2) apt-cache policy vim-gtk vim-gtk: Installed: 2:7.4.052-1ubuntu3 Candidate: 2:7.4.052-1ubuntu3 Version table: *** 2:7.4.052-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status 3) In your .vimrc or in a vim editing session, try adding the following: cab Q q This should make (and does in non-14.04 versions of vim) the typo command ':Q' work like the intended ':q'. 4) I have many other cab statements in my .vimrc, it's not specific to this example. Normal and Insert mode maps work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1380083/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Currently appears related to Bug #1284308. -- 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 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device
This also affects Ubuntu 14.04 Ubuntu 14.10 beta as of 11 October 2014. Lubuntu 14.10 beta is also affected, so this seems common to bluez as well as blueman. -- 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/1284308 Title: Bogus another operation in progress error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gnome-vfs-obexftp” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose bluetooth settings 3 - select the phone among the listed devices 4 - click on Browse files 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer = I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is another operation in progress. Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then ejected the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error This location could not be displayed. Another operation in progress, so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when ejecting the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1072191] Re: Preview ignores EXIF Orientation tag for jpegs
Still an issue in 14.04 / Unity 7.2.3 For me all thumbnails in the dash (in both file and photo lense) have the correct orientation, only when clicking on an item to open the larger preview, the preview has wrong orientation. See the attached screenshot. ** Attachment added: screenshot of preview (wrong orientation) and thumbnail (right orientation) https://bugs.launchpad.net/unity/+bug/1072191/+attachment/4231870/+files/dash-preview-orientation.png -- 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/1072191 Title: Preview ignores EXIF Orientation tag for jpegs Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Ubuntu 12.10 (quantal), Unity 6.8.0-0ubuntu2 Many (most?) cameras detect when a photo was taken while the camera was rotated, and store this in the JPEG EXIF Orientation tag. The preview view does not check the Orientation tag so many photographs, typically those in portrait format, are not rotated correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1072191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380178] [NEW] Google Hangouts Camera is upside down.
Public bug reported: I have tried every forum post and trick that I can find. I hope you can assist me. 1) Ubuntu 14.04.1 LTS Release 14.04 2) google-talkplugin 5.4.2.0-1 , google-chrome-beta 39.0.2171.19-1 3) When I start a video call or chat in Hangouts, the video image not to be inverted. 4) When I start a video call in Google Hangouts my image is inverted, however in Cheesebooth, I am not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Oct 11 15:49:58 2014 DistUpgraded: 2014-04-19 18:26:21,616 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1862] Subsystem: ASUSTeK Computer Inc. Device [1043:1862] InstallationDate: Installed on 2013-01-07 (642 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: ASUSTeK Computer Inc. P50IJ ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=dc19809e-34be-499c-a323-1dd1ce0fc337 ro splash quiet plymouth:debug=1=1=1=1=1=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-19 (174 days ago) dmi.bios.date: 02/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P50IJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd02/14/2011:svnASUSTeKComputerInc.:pnP50IJ:pvr1.0:rvnASUSTeKComputerInc.:rnP50IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P50IJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.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: Sat Oct 11 15:29:58 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21569 vendor SEC xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1380178 Title: Google Hangouts Camera is upside down. Status in “xorg” package in Ubuntu: New Bug description: I have tried every forum post and trick that I can find. I hope you can assist me. 1) Ubuntu 14.04.1 LTS Release 14.04 2) google-talkplugin 5.4.2.0-1 , google-chrome-beta 39.0.2171.19-1 3) When I start a video call or chat in Hangouts, the video image not to be inverted. 4) When I start a video call in Google Hangouts my image is inverted, however in Cheesebooth, I am not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Oct 11 15:49:58 2014 DistUpgraded: 2014-04-19 18:26:21,616 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1862] Subsystem: ASUSTeK Computer Inc. Device [1043:1862] InstallationDate: Installed on
[Touch-packages] [Bug 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
** Attachment added: sshd_config.remote https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+attachment/4231905/+files/sshd_config.remote -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 Status in “openssh” package in Ubuntu: New Bug description: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
** Attachment added: ssh_config.local https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+attachment/4231875/+files/ssh_config.local -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 Status in “openssh” package in Ubuntu: New Bug description: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353832] Re: arm CPUs get FATAL: cannot locate cpu MHz in /proc/cpuinfo
I've created a gist describing how to work around this. https://gist.github.com/rogerallen/0346a1812deda2a380da -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1353832 Title: arm CPUs get FATAL: cannot locate cpu MHz in /proc/cpuinfo Status in “jackd2” package in Ubuntu: Confirmed Bug description: Trying to run the Supercollider http://supercollider.github.io/ sound synthesis program on an ARM-based NVIDIA Jetson TK1, I received this error. I also received this when I tried jack_simple_client FATAL: cannot locate cpu MHz in /proc/cpuinfo This is from the Jack Library. $ apt-cache policy libjack-jackd2-0:armhf libjack-jackd2-0: Installed: 1.9.9.5+20130622git7de15e7a-1ubuntu1 Candidate: 1.9.9.5+20130622git7de15e7a-1ubuntu1 Version table: *** 1.9.9.5+20130622git7de15e7a-1ubuntu1 0 500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main armhf Packages 100 /var/lib/dpkg/status (updated in 2013) The issue is fixed in the latest source by this checkin: (from March, 2014) https://github.com/jackaudio/jack2/commit/d425d8035b761b4a362c538c41eca874ff4995f0 I have found this latest source works for me if I compile and install jack by hand. So, I think updating the libjack-jackd2-0:armhf library would be desirable. Until then, all ARM-based systems can't use jack. Also see https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1347914 for a similar report for the program Audacity. Additional details $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ uname -a Linux muggy 3.10.24-gf455cd4-dirty #3 SMP PREEMPT Tue Jul 22 12:20:38 PDT 2014 armv7l armv7l armv7l GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1353832/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380192] [NEW] Usermetrics overlaps onto lock screen
Public bug reported: See screenshots. When you swipe away the user metrics welcome screen, if you have a large circle (representing a lot of calls / sms etc) on the right (and maybe left) it bleeds over into the lock screen. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: device-2014-10-11-234203.png https://bugs.launchpad.net/bugs/1380192/+attachment/4231989/+files/device-2014-10-11-234203.png -- 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/1380192 Title: Usermetrics overlaps onto lock screen Status in “unity8” package in Ubuntu: New Bug description: See screenshots. When you swipe away the user metrics welcome screen, if you have a large circle (representing a lot of calls / sms etc) on the right (and maybe left) it bleeds over into the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380192] Re: Usermetrics overlaps onto lock screen
** Attachment added: device-2014-10-11-234211.png https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380192/+attachment/4231990/+files/device-2014-10-11-234211.png -- 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/1380192 Title: Usermetrics overlaps onto lock screen Status in “unity8” package in Ubuntu: New Bug description: See screenshots. When you swipe away the user metrics welcome screen, if you have a large circle (representing a lot of calls / sms etc) on the right (and maybe left) it bleeds over into the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310260] Re: Pulseaudio fails to detect card (probably due to hybrid graphics)
Suggestion on post #27 by Letik (martin-96-59) incluning the : options snd-hda-intel enable=0,1,0 on file /etc/modprobe.d/alsa-base.conf works for me too. -- 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/1310260 Title: Pulseaudio fails to detect card (probably due to hybrid graphics) Status in “alsa-driver” package in Ubuntu: Triaged Bug description: Hi, I wanted to install Trusty on my Elitebook 850 G1 with hybrid graphics (Intel / AMD) but pulseaudio goes nuts on me as soon as I try to play any music / sound, try to change volume, etc. I've tried it with Ubuntu, Kubuntu and now with Xubuntu with the same result everytime. My guess is that pulseaudio has problems with the AMD GPU and it's sound processor being switched off automatically as enabled by Kernel 3.13 (formerly achieved by adding the radeon.runpm=1 kernel parameter) (http://lists.freedesktop.org/archives/dri-devel/2013-September/045650.html) root@HP-EliteBook-850-G1:~# cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr::00:02.0 1:DIS: :DynOff::03:00.0 2:DIS-Audio: :Off::03:00.1 As you can see, the AMD GPU has been turned off automatically. Pulseaudio, the (X)Ubuntu volume applet and KMix on the other hand list it as still available. Based on that I asume pulseaudio tries to access a switched-off device and fails. I've followed the steps listed here: https://wiki.ubuntu.com/DebuggingSoundProblems and here: https://wiki.ubuntu.com/PulseAudio/Log I'll attach the logs right away. (pulseverbose1.log and my dmesg output) Pusleverbose is full of messages like this one: ( 0.013| 0.000) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:0: No such file or directory This output of dmesg also caught my attention: [ 354.927935] HDMI ATI/AMD: no speaker allocation for ELD [ 357.695010] hda-intel :03:00.1: Disabling via VGA-switcheroo One thing I noticed using Kubuntu is that after pulseaudio becomes unresponsive the taskmanager lists 4 pulseaudio processes two of which are active on harddrive (Aktiv auf Festplatte). Those two processes cannot be killed even as root. Currently being on Xubuntu the same thing is true, although it lists only one process in the taskmanager that cannot be killed. I hope you can help me. Best regards, Paul ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Sun Apr 20 13:47:09 2014 InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP EliteBook 850 G1, IDT 92HD91BXX, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.08 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.54 dmi.chassis.asset.tag: CNU345BY96 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.08:bd02/19/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3008CC10003:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 850 G1 dmi.product.version: A3008CC10003 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1310260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334329] Re: Sound input settings not saved
https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_cirrus.c?id=1077a024812d3b2d76a7a371df75795a276d9dd8 you need to file an upstream bug report capture source still create when using hda-emu and latest patched driver spec-gen.line_in_auto_switch =1; similar to https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_sigmatel.c?id=e8b99a1dcb49b0d362b19a4831a00d85c76bd4b3 -- 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/1334329 Title: Sound input settings not saved Status in “alsa-driver” package in Ubuntu: New Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: When attempting to set my preferred sound input device, simply leaving sound preferences and going back to sound preferences, and selecting input, causes the default SPDIF to be selected again, and not the internal microphone I preferred. I made a video to demonstrate what I mean by this here: http://youtu.be/9Q9EQvLl_rA 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center I really don't know. It's just the sound preferences. 3) What you expected to happen For my selected sound input to be saved. 4) What happened instead Keeps defaulting to the top sound input ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: brandon 23953 F pulseaudio /dev/snd/controlC0: brandon 23953 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 25 11:20:14 2014 InstallationDate: Installed on 2014-04-26 (60 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334329] Re: Sound input settings not saved
Once again, I do not understand any of this. You're asking me to do this but I am just a casual user who wrote this bug report because me, like others, are experiencing this only on Ubuntu. If you can ELI5 (explain like I'm 5), I might be able to do something. Otherwise if not, I give up and will abandon all hope here. Linux should not require a user to be basically a programmer to fix something stupid like a built in microphone on my computer. -- 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/1334329 Title: Sound input settings not saved Status in “alsa-driver” package in Ubuntu: New Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: When attempting to set my preferred sound input device, simply leaving sound preferences and going back to sound preferences, and selecting input, causes the default SPDIF to be selected again, and not the internal microphone I preferred. I made a video to demonstrate what I mean by this here: http://youtu.be/9Q9EQvLl_rA 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center I really don't know. It's just the sound preferences. 3) What you expected to happen For my selected sound input to be saved. 4) What happened instead Keeps defaulting to the top sound input ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: brandon 23953 F pulseaudio /dev/snd/controlC0: brandon 23953 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 25 11:20:14 2014 InstallationDate: Installed on 2014-04-26 (60 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1331753] Re: Network manager caches previously seen access points too long
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete = Expired -- 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/1331753 Title: Network manager caches previously seen access points too long Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Expired Bug description: Using mako #87. Enable wifi on deivce. Go for a drive to a friend or relatives house where they have wifi. When you arrive, pull down the network indicator and try to find the access point. What you should see is a small number of access points nearby, with the strongest signal ones being obvious. What actually happens is for some time you see every access point the phone saw along the journey between locations. See video:- https://www.youtube.com/watch?v=lQMLik-WH5o I would expect the number of access points listed to age/decay faster. I guess we haven't noticed this before on the desktop because people don't usually do what I did with a laptop/desktop. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu18 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Wed Jun 18 20:30:02 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2014-06-18 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140618) IpRoute: default via 192.168.1.1 dev wlan0 proto static 10.145.38.0/24 dev rmnet_usb1 proto kernel scope link src 10.145.38.242 metric 13 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.105 metric 9 PciNetwork: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 2014-06-11T20:47:57 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 /ril_0 gsm connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1331753/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
