[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Any update on this? I'd love the get the touchpad working properly. -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367004] [NEW] [MIR] python-gnupg
Public bug reported: Availability: % apt-cache show python-gnupg | grep -i section Section: universe/python Rationale: As shown here: http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg python-gnupg is a run-time dependency of system-image, which is the system upgrader for, and seeded into Ubuntu Touch. Security, QA The package is well supported upstream, in Debian, and in Ubuntu. LP: #1283783 describes an upgrading bug, but I have not yet investigated it. UI standards: n/a Dependencies: None that aren't already in main. Standards compliance: No known issues. Maintenance: No known issues. This is the generally accepted best gnupg wrapper for Python. It supports both Python 2 and 3. ** Affects: python-gnupg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1367004 Title: [MIR] python-gnupg Status in “python-gnupg” package in Ubuntu: New Bug description: Availability: % apt-cache show python-gnupg | grep -i section Section: universe/python Rationale: As shown here: http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg python-gnupg is a run-time dependency of system-image, which is the system upgrader for, and seeded into Ubuntu Touch. Security, QA The package is well supported upstream, in Debian, and in Ubuntu. LP: #1283783 describes an upgrading bug, but I have not yet investigated it. UI standards: n/a Dependencies: None that aren't already in main. Standards compliance: No known issues. Maintenance: No known issues. This is the generally accepted best gnupg wrapper for Python. It supports both Python 2 and 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-gnupg/+bug/1367004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283783] Re: Error upgrading python3-gnupg
http://bugs.python.org/issue19021 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1283783 Title: Error upgrading python3-gnupg Status in “python-gnupg” package in Ubuntu: Fix Released Bug description: Setting up python3-gnupg (0.3.6-1) ... Exception ignored in: bound method Popen.__del__ of subprocess.Popen object at 0xb707418c Traceback (most recent call last): File /usr/lib/python3.4/subprocess.py, line 897, in __del__ TypeError: 'NoneType' object is not callable Exception ignored in: bound method Popen.__del__ of subprocess.Popen object at 0xb707426c Traceback (most recent call last): File /usr/lib/python3.4/subprocess.py, line 897, in __del__ TypeError: 'NoneType' object is not callable Setting up python3-pyparsing (2.0.1+dfsg1-1build1) ... Setting up python-dirspec (13.10-0ubuntu2) ... Setting up python3-dirspec (13.10-0ubuntu2) ... Processing triggers for libc-bin (2.18-0ubuntu7) ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3-gnupg 0.3.6-1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: Unity Date: Sun Feb 23 20:08:49 2014 InstallationDate: Installed on 2014-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140208) PackageArchitecture: all SourcePackage: python-gnupg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-gnupg/+bug/1283783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283783] Re: Error upgrading python3-gnupg
I think this is no longer a bug. This is related to Python issue 19021 and all fixes were cherry picked into 3.4.0, which Trusty and Utopic have. If you are still able to reproduce it, please reopen the bug and provide a recipe on whichever version of Ubuntu you're using. Thanks! ** Changed in: python-gnupg (Ubuntu) Status: Confirmed = Fix Released ** Bug watch added: Python Roundup #19021 http://bugs.python.org/issue19021 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1283783 Title: Error upgrading python3-gnupg Status in “python-gnupg” package in Ubuntu: Fix Released Bug description: Setting up python3-gnupg (0.3.6-1) ... Exception ignored in: bound method Popen.__del__ of subprocess.Popen object at 0xb707418c Traceback (most recent call last): File /usr/lib/python3.4/subprocess.py, line 897, in __del__ TypeError: 'NoneType' object is not callable Exception ignored in: bound method Popen.__del__ of subprocess.Popen object at 0xb707426c Traceback (most recent call last): File /usr/lib/python3.4/subprocess.py, line 897, in __del__ TypeError: 'NoneType' object is not callable Setting up python3-pyparsing (2.0.1+dfsg1-1build1) ... Setting up python-dirspec (13.10-0ubuntu2) ... Setting up python3-dirspec (13.10-0ubuntu2) ... Processing triggers for libc-bin (2.18-0ubuntu7) ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: python3-gnupg 0.3.6-1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: Unity Date: Sun Feb 23 20:08:49 2014 InstallationDate: Installed on 2014-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140208) PackageArchitecture: all SourcePackage: python-gnupg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-gnupg/+bug/1283783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367028] [NEW] [MIR] system-image
Public bug reported: Availability: universe Rationale: system-image is the client for image based upgrades. It is a core component and thus seeded in Ubuntu Touch. Security: No known issues. QA: Well supported upstream and in Ubuntu. Package has build-time unittests and DEP-8 tests. UI standards: n/a Dependencies: All non-main build- and run-time dependencies already or will soon have MIRs. Standards compliance: No known issues. Maintenance: No known issues. ** Affects: system-image (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1367028 Title: [MIR] system-image Status in “system-image” package in Ubuntu: New Bug description: Availability: universe Rationale: system-image is the client for image based upgrades. It is a core component and thus seeded in Ubuntu Touch. Security: No known issues. QA: Well supported upstream and in Ubuntu. Package has build-time unittests and DEP-8 tests. UI standards: n/a Dependencies: All non-main build- and run-time dependencies already or will soon have MIRs. Standards compliance: No known issues. Maintenance: No known issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1367028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1367028] Re: [MIR] system-image
On Sep 09, 2014, at 03:22 PM, Michael Terry wrote: What's the rationale for moving to main now? I didn't think we were trying to mass-promote Touch packages yet. http://people.canonical.com/~ubuntu-archive/component-mismatches- proposed.svg (There's been discussion about image based upgrades for server and desktop.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1367028 Title: [MIR] system-image Status in “system-image” package in Ubuntu: Incomplete Bug description: Availability: universe Rationale: system-image is the client for image based upgrades. It is a core component and thus seeded in Ubuntu Touch. Security: No known issues. QA: Well supported upstream and in Ubuntu. Package has build-time unittests and DEP-8 tests. UI standards: n/a Dependencies: All non-main build- and run-time dependencies already or will soon have MIRs. Standards compliance: No known issues. Maintenance: No known issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1367028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
auto_download = wifi only device is on wifi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): Incomplete Status in “system-image” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
Here's what I see on krillin r26. * Go to System Settings * When an update is available, click on Updates available (not the Updates icon) * When the update is done downloading, click on Not Now * I'm left on the Updates page (still showing r26) * Hit back arrow to return to System Settings * Wait 2 minutes * Click on Updates available again * I see the progress meters stuck on 0% but then eventually I get prompted to do an Update System * No system-image or system-setting crash file, and system-image-dbus is still running # system-image-cli --info current build number: 9 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-09-01 04:08:48 version version: 9 version ubuntu: 20140901 version device: 20140829-678239d Not sure why system settings says I'm on r26 but --info says 9. I am now going to try to upgrade and see what happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): Incomplete Status in “system-image” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
Hmm, maybe I was on 9 and it offered to upgrade me to 26. I'm definitely on 26 now. Trying recipe again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): Incomplete Status in “system-image” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
On Sep 09, 2014, at 09:33 PM, Pat McGowan wrote: Any chance bug 1324612 is related? Its a slightly different scenario where update was never downloaded afaik You'd think not, since system-settings is a different process than system-image. But right now I can't say for sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): Incomplete Status in “system-image” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
Okay, so after setting .writable_image and hacking channel.ini to think it's r25 instead of r26. I can reproduce the crash file. I'm seeing some weird behavior though coming from the dbus api via system-settings. Not enough to report them, but it does make me think that some s-s behavior has changed, which is triggering this problem. Could be a latent race window now hit by s-s where it wasn't before. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): Incomplete Status in “system-image” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
Note that you do not even have to hit Not Now for the crash to occur. You'll get the crash file even while this dialog is still on the screen. I instrumented systemimage/dbus.py and here's something very interesting: [systemimage] Sep 09 22:05:19 2014 (13932) Update is downloading [systemimage] Sep 09 22:05:20 2014 (13932) all files available in /android/cache/recovery [systemimage] Sep 09 22:05:20 2014 (13932) preparing recovery [systemimage] Sep 09 22:05:20 2014 (13932) Update downloaded [systemimage] Sep 09 22:05:20 2014 (13932) release checking lock from _download() [systemimage] Sep 09 22:05:20 2014 (13932) released! [systemimage] Sep 09 22:05:20 2014 (13932) - DU [systemimage] Sep 09 22:05:20 2014 (13932) - DU [systemimage] Sep 09 22:05:20 2014 (13932) - DU [systemimage] Sep 09 22:05:20 2014 (13932) Update is downloading [systemimage] Sep 09 22:05:20 2014 (13932) Update downloaded [systemimage] Sep 09 22:05:20 2014 (13932) release checking lock from _download() [systemimage] Sep 09 22:05:20 2014 (13932) Update is downloading [systemimage] Sep 09 22:05:20 2014 (13932) Update downloaded [systemimage] Sep 09 22:05:20 2014 (13932) release checking lock from _download() [systemimage] Sep 09 22:05:20 2014 (13932) Update is downloading [systemimage] Sep 09 22:05:20 2014 (13932) Update downloaded [systemimage] Sep 09 22:05:20 2014 (13932) release checking lock from _download() What this is telling me is that CheckForUpdate is being called, the update is downloaded (since I'm on wifi), and all files are available. It tries to release the checking lock, and it gets released. So far so good. Next, system-settings calls DownloadUpdate three times in a row! I have no idea why. Because DownloadUpdate was called without calling CheckForUpdate, when the download is complete (as it is almost immediately because all the files are already available), it will try to release the checking lock, which was never acquired, since it's only acquired in CFU. I need to think on the right fix for this, but it probably involves a downloading lock as well, and perhaps a guard around the checking lock. Anyway, I think I have enough information to reproduce this in a test case. ** Changed in: ubuntu-system-image Status: Incomplete = Triaged ** Changed in: ubuntu-system-image Assignee: (unassigned) = Barry Warsaw (barry) ** Changed in: ubuntu-system-image Importance: Undecided = Critical ** Changed in: ubuntu-system-image Milestone: None = 2.3.3 ** Changed in: ubuntu-system-image Status: Triaged = In Progress ** Changed in: ubuntu-system-image Milestone: 2.3.3 = 2.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
BTW, I seem to have to click Not Now three times to dismiss the dialog. Something tells me this is related to the system settings changes. I'll leave those bugs for another day, but system-image-dbus should still be robust against any system settings craziness. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367028] Re: [MIR] system-image
I have a branch that removes tox and its sub-dependencies as b-ds for system-image. I'll release it in a s-i 2.4 to come in the next few days hopefully. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1367028 Title: [MIR] system-image Status in “system-image” package in Ubuntu: New Bug description: Availability: universe Rationale: system-image is the client for image based upgrades. It is a core component and thus seeded in Ubuntu Touch. Security: No known issues. QA: Well supported upstream and in Ubuntu. Package has build-time unittests and DEP-8 tests. UI standards: n/a Dependencies: All non-main build- and run-time dependencies already or will soon have MIRs. Standards compliance: No known issues. Maintenance: No known issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1367028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
On Sep 10, 2014, at 02:39 PM, Ken VanDine wrote: But there must be a bug in s-i-d too causing it to crash if it gets a download request for an update that is already downloaded. That aligns with my analysis of s-i-d. This bug task for system-image is to make DownloadUpdate robust in that case; i.e. not crash, but emit an UpdateDownloaded signal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
Not that you care, but it's tricky to craft a test case for this because the crash doesn't actually affect any behavior! Since the UpdateDownloaded signal is emitted before the checking lock is released, everything still works. The only effect is that s-i-d tracebacks, and you only see that in the crash report because of the way dbus-python's error handling works. This probably means that the best thing to do is just explicitly swallow any exceptions from .release(). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
More fun: I've verified that when this .crash file gets written, the si- dbus process does *not* exit. That seems crazy right? Here's what I think is happening. PyErr_Print() calls PyErr_PrintEx(1), and the latter does sys.excepthook processing. There are several places within dbus-python that calls PyErr_Print(). I haven't gdb'd the process but my guess is that the exception-in-@method case causes a PyErr_Print() but clears, gasp ignores, or otherwise arranges for the exception to not propagate to the Python main loop or otherwise cause the process to exit. Since apport hooks into sys.excepthook to write the .crash file, that's how you get the crash without exiting the si-dbus process. How to test the darn thing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365761] Re: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image-cli@9:main:last_update_date
** Also affects: ubuntu-system-image Importance: Undecided Status: New ** Tags added: client -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365761 Title: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image- cli@9:main:last_update_date Status in Ubuntu system image (server/client/updater): New Status in “system-image” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/93cf5f63dff546a6b8c281292cc2598ceceb473c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
** Branch linked: lp:~barry/ubuntu-system-image/lp1365646 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
** Changed in: ubuntu-system-image Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): Fix Committed Status in “system-image” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365761] Re: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image-cli@9:main:last_update_date
** Changed in: system-image (Ubuntu) Status: New = Triaged ** Changed in: system-image (Ubuntu) Assignee: (unassigned) = Barry Warsaw (barry) ** Changed in: ubuntu-system-image Status: New = In Progress ** Changed in: ubuntu-system-image Importance: Undecided = High ** Changed in: ubuntu-system-image Assignee: (unassigned) = Barry Warsaw (barry) ** Changed in: ubuntu-system-image Milestone: None = 2.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365761 Title: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image- cli@9:main:last_update_date Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/93cf5f63dff546a6b8c281292cc2598ceceb473c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365761] Re: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image-cli@9:main:last_update_date
** Changed in: ubuntu-system-image Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365761 Title: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image- cli@9:main:last_update_date Status in Ubuntu system image (server/client/updater): Fix Committed Status in “system-image” package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/93cf5f63dff546a6b8c281292cc2598ceceb473c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349234] Re: Input still received when locked if audio device plugged in
** Summary changed: - Input still recieved when locked if audio device plugged in + Input still received when locked if audio device plugged in -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1349234 Title: Input still received when locked if audio device plugged in Status in “system-image” package in Ubuntu: New Bug description: If you lock a device while an audio device is plugged in to the audio port and music is playing, touch events keep getting recieved even though the device looks non-responsive. Tried to replicate in various other applications (browser with youtube-video, media-player with music video) but they don't seem to be affected, so this may be specific to the core music app. Easily replicateable on my nexus 4: open music app play any song lock phone touch screen unlock wah laa. Version: Ubuntu 14.10 (r133) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1349234/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1321481] Re: run integration tests from autopkgtest
** Changed in: ubuntu-system-image Milestone: 2.4 = None ** No longer affects: ubuntu-system-image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1321481 Title: run integration tests from autopkgtest Status in “system-image” package in Ubuntu: Triaged Bug description: system-image is a critical piece of infrastructure that needs to be kept in working order; changes should not be allowed to land in the archive that break it, since that risks leaving users high and dry on a phone image that's not upgradable. The best way to guard against this is by having system-image run a full battery of integration tests (including real system-image updates using ubuntu-emulator) from autopkgtest. This will prevent any direct dependencies of system-image from regressing system-image's functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1321481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
** Changed in: ubuntu-system-image Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): Fix Released Status in “system-image” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365761] Re: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image-cli@9:main:last_update_date
** Changed in: ubuntu-system-image Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365761 Title: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image- cli@9:main:last_update_date Status in Ubuntu system image (server/client/updater): Fix Released Status in “system-image” package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/93cf5f63dff546a6b8c281292cc2598ceceb473c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
** Changed in: system-image (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): Fix Released Status in “system-image” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365761] Re: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image-cli@9:main:last_update_date
** Changed in: system-image (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365761 Title: /usr/bin/system-image-cli:PermissionError:/usr/bin/system-image- cli@9:main:last_update_date Status in Ubuntu system image (server/client/updater): Fix Released Status in “system-image” package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/93cf5f63dff546a6b8c281292cc2598ceceb473c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371703] Re: No fallback if the system update process fails at any point
I agree it's critical to think about. At the lowest level of the above stack, a shell + system-image-cli + networking should be able to update the device, but it's probably not super easy for the average user. I can imagine a small script that would use adb to shell in and run the update. If the device's network is down, then I can also imagine that script could optionally push all the data and keyring files obtained in some other way (e.g. via a web site visited on the host). Once the device is attached to USB, this script would push the files into the right place and invoke s-i-cli over adb. ** Also affects: ubuntu-system-image Importance: Undecided Status: New ** Tags added: client -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1371703 Title: No fallback if the system update process fails at any point Status in Ubuntu system image (server/client/updater): New Status in “system-image” package in Ubuntu: New Bug description: For someone to install a system update, all of the following need to be true: (A) The phone needs to start up completely. (B) Unity needs to not crash. (C) The networking stack needs to let Ubuntu check for updates. (D) If System Settings is not in the Launcher, the Apps scope needs to not crash. (E) System Settings needs to launch without crashing. (F) The System Settings Updates screen needs to open without crashing. (G) The system-image update system itself needs to work properly. This is a long and brittle chain. If *any one* of these steps breaks, the phone is no longer updateable. And at worst -- if A, B, or C fails -- the phone is effectively bricked. This is not a theoretical problem. On Ubuntu for PC, crasher bugs in update-manager often persist for a long time in the list of most common errors, because the updates that fix them can't themselves be installed until a nearby geek cracks out a terminal to use apt-get. That's not so practical on a phone. Therefore, there should be a fallback path for installing system image updates in emergency situations. This path may not avoid all of the requirements listed above, but it should avoid as many as practical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1371703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367907] Re: Segfault in gc with cyclic trash
** Changed in: python3.4 (Ubuntu) Status: New = In Progress ** Changed in: python3.4 (Ubuntu) Importance: Undecided = High ** Changed in: python3.4 (Ubuntu) Assignee: (unassigned) = Barry Warsaw (barry) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1367907 Title: Segfault in gc with cyclic trash Status in Messaging API for OpenStack: New Status in Python: Fix Released Status in “python3.4” package in Ubuntu: In Progress Bug description: Trusty's python3.4 package is affected by python bug http://bugs.python.org/issue21435. This bug was fixed in http://hg.python.org/cpython/rev/64ba3f2de99c. Trusty should pull this fix into the python3.4 package. Note this definitely affects some python projects. `git clone https://git.openstack.org/openstack/oslo.messaging cd oslo.messaging edit tox.ini file, copy py33 target and rename to py34 tox -repy34` will segfault due to this bug. With previous versions of python unaffected by this bug there is no segfaulting. Now for details, broken using: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy python3.4 python3.4: Installed: 3.4.0-2ubuntu1 Candidate: 3.4.0-2ubuntu1 Version table: *** 3.4.0-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status If I install the following python3.4 packages for Unicorn on Trusty this bug is corrected. The Unicorn packages here on lp for python3.4 are python3.4.1 which includes the bug fix for this bug. libpython3.4_3.4.1-10ubuntu1_amd64.deb libpython3.4-dev_3.4.1-10ubuntu1_amd64.deb libpython3.4-stdlib_3.4.1-10ubuntu1_amd64.deb python3.4-dbg_3.4.1-10ubuntu1_amd64.deb python3.4-minimal_3.4.1-10ubuntu1_amd64.deb libpython3.4-dbg_3.4.1-10ubuntu1_amd64.deb libpython3.4-minimal_3.4.1-10ubuntu1_amd64.deb python3.4_3.4.1-10ubuntu1_amd64.deb python3.4-dev_3.4.1-10ubuntu1_amd64.deb Note I installed the -dbg packages too just in case I needed to use gdb but that wasn't necessary as the test case works with these newer versions of python. $ apt-cache policy python3.4 python3.4: Installed: 3.4.1-10ubuntu1 Candidate: 3.4.1-10ubuntu1 Version table: *** 3.4.1-10ubuntu1 0 100 /var/lib/dpkg/status 3.4.0-2ubuntu1 0 500 http://az2.clouds.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages [Impact] This python bug can cause python processes that tickle it to segfault python. This means there could be a significant number of python packages that are broken when run under this interpreter. The fix for this bug should be backported to avoid seemingly random and hard to debug segfaults from happening when users use python. Unicorn's 3.4.1 packages fix this bug by including the patch at http://hg.python.org/cpython/rev/64ba3f2de99c. [Test Case] There is a test case detailed in the upstream bug http://bugs.python.org/issue21435, though I have been doing the following instead: git clone https://git.openstack.org/openstack/oslo.messaging cd oslo.messaging git fetch https://review.openstack.org/openstack/oslo.messaging refs/changes/90/118790/2 git checkout FETCH_HEAD tox -repy34 # This should end with segfaulting test runners. Note if you don't have tox installed you will need to install version 1.7.2 or greater. `sudo pip install tox==1.7.2` will do this. [Regression Potential] The patch in question is small. If we go straight to python 3.4.1 the diff will be larger but that isn't necessary to fix this particular issue. The biggest regression potential would be that the garbage collector is newly broken by the this bug fix. Considering that the garbage collector is already broken and this patch comes with test cases to check it is less broken the risk of regression here is less than the pain of dealing with this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.messaging/+bug/1367907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290847] Re: pyvenv fails due to mising ensurepip module
I apologize for going back and forth on this bug so often. It may simply be not feasible to SRU a fix for this. The fix is not just in the python3.4 package. I think at a minimum this means: * Backporting wheel to trusty. It was first available in utopic, so i'm not even sure if it's appropriate to sru a package that doesn't exist in the target version. It won't help to add it to -backports. * Backport chardet, colorama, distlib, html5lib, pip, requests, setuptools, six, and urllib3, at least such that they add their -whl binary packages (e.g. /usr/share/python-wheels/*.whl) * Backport the fix for python3.4 Given that `virtualenv -p python3` effectively does the same thing, is it worth it? Seems like a tall order. Is there anything that venv gives you that you *don't* get for virtualenv? I could see fixing `python3 -m venv` to write an error message pointing people at virtualenv. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module Status in “python3-defaults” package in Ubuntu: Fix Released Status in “python3.4” package in Ubuntu: Fix Released Status in “python3.4” package in Debian: Fix Released Bug description: Hello, I noticed the following # fails python3.4 -m venv --clear python-venv Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 # works, but no pip python3.4 -m venv --clear --without-pip python-venv Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290847] Re: pyvenv fails due to mising ensurepip module
infinity barry: Kay, if they wouldn't be 100% compatible, I agree it's a bad idea, so just printing the yo, this is broken, try the other thing would be fine, IMO. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module Status in “python3-defaults” package in Ubuntu: Fix Released Status in “python3.4” package in Ubuntu: Fix Released Status in “python3.4” package in Debian: Fix Released Bug description: Hello, I noticed the following # fails python3.4 -m venv --clear python-venv Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 # works, but no pip python3.4 -m venv --clear --without-pip python-venv Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1290847] Re: pyvenv fails due to mising ensurepip module
On Sep 22, 2014, at 07:44 PM, Donald Stufft wrote: Can we just add the Wheel files to ensurepip for Trusty? It's already being done for virtualenv (which is why it works at all) and that should be way less impact than having to do the full backport that the other thing would require. I'm not sure that helps much, since to build the wheels, we still need to backport all those packages. I don't think it will be acceptable to just slide the .whl files into python3.4 since we'd still be violating the rule of including files not built from source. One thing we could do though is only complain if --with-pip is included. Yeah, it's the default, but if someone explicitly calls --without-pip, it would work (since ensurepip isn't invoked). I guess that's only marginally better. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module Status in “python3-defaults” package in Ubuntu: Fix Released Status in “python3.4” package in Ubuntu: Fix Released Status in “python3.4” package in Debian: Fix Released Bug description: Hello, I noticed the following # fails python3.4 -m venv --clear python-venv Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 # works, but no pip python3.4 -m venv --clear --without-pip python-venv Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290847] Re: pyvenv fails due to mising ensurepip module
The PPA version doesn't fix this problem. I have a workaround for this bug, and a fix for LP: #1367907 that would both be appropriate to SRU. I'll get together with Doko to get him my patches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module Status in “python3-defaults” package in Ubuntu: Fix Released Status in “python3.4” package in Ubuntu: Fix Released Status in “python3.4” package in Debian: Fix Released Bug description: Hello, I noticed the following # fails python3.4 -m venv --clear python-venv Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 # works, but no pip python3.4 -m venv --clear --without-pip python-venv Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290847] Re: pyvenv fails due to mising ensurepip module
debdiff sent to Doko -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module Status in “python3-defaults” package in Ubuntu: Fix Released Status in “python3.4” package in Ubuntu: Fix Released Status in “python3.4” package in Debian: Fix Released Bug description: Hello, I noticed the following # fails python3.4 -m venv --clear python-venv Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 # works, but no pip python3.4 -m venv --clear --without-pip python-venv Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348393] Re: OpenAL 1.15.x Breaks Multiarch (makes 32-bit wine uninstallable on 64-bit system)
Thanks for the workaround. As I haven't a clue what roaraudio is, I'll probably never need it. I have wine back again in Utopic! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openal-soft in Ubuntu. https://bugs.launchpad.net/bugs/1348393 Title: OpenAL 1.15.x Breaks Multiarch (makes 32-bit wine uninstallable on 64-bit system) Status in “openal-soft” package in Ubuntu: Confirmed Status in “roaraudio” package in Ubuntu: Triaged Status in “roaraudio” package in Debian: New Bug description: When 1 install's OpenAL which was a resent upgrade it removes a program called wine and after it is done installed if you try to reinstall Wine it says its broken. When ya remove Open-AL and reinstall Wine it wants to remove the entire Ubuntu Desktop components that make it. theres a History log of Upgrade progress below --- ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 2279 F pulseaudio /dev/snd/controlC0: darkangel 2279 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=a22cc369-bf57-44d6-88c0-2de766873fd6 InstallationDate: Installed on 2014-07-20 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: eMachines EL1360G NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 RelatedPackageVersions: linux-restricted-modules-3.16.0-5-generic N/A linux-backports-modules-3.16.0-5-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/1348393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349478] Re: /usr/sbin/system-image-dbus:sqlite3.OperationalError:_check_for_update:emit_signal:UpdateAvailableStatus:__init__:__enter__:_cursor
** Also affects: ubuntu-system-image Importance: Undecided Status: New ** Tags added: client ** Changed in: ubuntu-system-image Assignee: (unassigned) = Barry Warsaw (barry) ** Changed in: system-image (Ubuntu) Assignee: (unassigned) = Barry Warsaw (barry) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1349478 Title: /usr/sbin/system-image- dbus:sqlite3.OperationalError:_check_for_update:emit_signal:UpdateAvailableStatus:__init__:__enter__:_cursor Status in Ubuntu system image (server/client/updater): New Status in “system-image” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3c165791331447a1d55f0488cad6904f6e63988d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1349478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349478] Re: /usr/sbin/system-image-dbus:sqlite3.OperationalError:_check_for_update:emit_signal:UpdateAvailableStatus:__init__:__enter__:_cursor
** Changed in: ubuntu-system-image Importance: Undecided = High ** Changed in: ubuntu-system-image Status: New = In Progress ** Changed in: ubuntu-system-image Milestone: None = 2.3.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1349478 Title: /usr/sbin/system-image- dbus:sqlite3.OperationalError:_check_for_update:emit_signal:UpdateAvailableStatus:__init__:__enter__:_cursor Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3c165791331447a1d55f0488cad6904f6e63988d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1349478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349478] Re: /usr/sbin/system-image-dbus:sqlite3.OperationalError:_check_for_update:emit_signal:UpdateAvailableStatus:__init__:__enter__:_cursor
This is very likely caused by the same issue as LP: #1301995 - specifically that the tests are being run as non-root, but they still try to write the settings.db file into /var/lib/system-image (which is only root:root writable). I don't believe this will affect any actual touch images, just Q/A. Still, it's an easy fix; we'll use ~/.cache /system-image/lib/settings.db in that case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1349478 Title: /usr/sbin/system-image- dbus:sqlite3.OperationalError:_check_for_update:emit_signal:UpdateAvailableStatus:__init__:__enter__:_cursor Status in Ubuntu system image (server/client/updater): In Progress Status in “system-image” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3c165791331447a1d55f0488cad6904f6e63988d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1349478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349478] Re: /usr/sbin/system-image-dbus:sqlite3.OperationalError:_check_for_update:emit_signal:UpdateAvailableStatus:__init__:__enter__:_cursor
** Changed in: ubuntu-system-image Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1349478 Title: /usr/sbin/system-image- dbus:sqlite3.OperationalError:_check_for_update:emit_signal:UpdateAvailableStatus:__init__:__enter__:_cursor Status in Ubuntu system image (server/client/updater): Fix Released Status in “system-image” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/3c165791331447a1d55f0488cad6904f6e63988d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1349478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351373] Re: Crashed during s-i's test_pause during a local test build of s-i
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1351373 Title: Crashed during s-i's test_pause during a local test build of s-i Status in “ubuntu-download-manager” package in Ubuntu: New Bug description: I think this crashed when sending a 'pause' signal to u-d-m, but I will try to gather more information. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: ubuntu-download-manager 0.7+14.10.20140725-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 Date: Fri Aug 1 11:54:06 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/ubuntu-download-manager InstallationDate: Installed on 2011-07-12 (1115 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1) ProcCmdline: /usr/bin/ubuntu-download-manager -self-signed-certs /build/system-image-g5L18v/system-image-2.3.2/systemimage/tests/data/cert.pem -disable-timeout -stoppable -log-dir /tmp/tmp7qo6was_ ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/sh LD_PRELOAD=set PATH=(custom, no user) TERM=xterm Signal: 6 SourcePackage: ubuntu-download-manager SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to utopic on 2011-12-23 (951 days ago) UserGroups: adm admin autopilot cdrom dialout fuse libvirtd lpadmin plugdev sambashare sbuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1351373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1063350] Re: curl corrupts floating point context
On Oct 14, 2014, at 01:19 PM, ינון-דוד-צדוק (Yinon-David-Zadok) wrote: I think that #41 is right (Athlon cpu is causing it) my cpu: AMD Sempron(tm) 2400+ But is it still reproducible on Ubuntu 14.10 with the latest PyCURL? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1063350 Title: curl corrupts floating point context Status in “pycurl” package in Ubuntu: Incomplete Status in “pycurl” source package in Precise: New Status in “pycurl” source package in Trusty: Incomplete Status in “pycurl” source package in Utopic: Incomplete Bug description: # add-apt-repository ppa:ubuntu-wine/ppa You are about to add the following PPA to your system: Welcome to the Wine Team PPA. Here you can get the latest available Wine betas for every supported version of Ubuntu. This PPA is managed by Scott Ritchie and Maarten Lankhorst. More info: https://launchpad.net/~ubuntu-wine/+archive/ppa Press [ENTER] to continue or ctrl-c to cancel adding it Exception in thread Thread-1: Traceback (most recent call last): File /usr/lib/python2.7/threading.py, line 551, in __bootstrap_inner self.run() File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 99, in run self.add_ppa_signing_key(self.ppa_path) File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 132, in add_ppa_signing_key tmp_keyring_dir = tempfile.mkdtemp() File /usr/lib/python2.7/tempfile.py, line 322, in mkdtemp name = names.next() File /usr/lib/python2.7/tempfile.py, line 141, in next letters = [choose(c) for dummy in 123456] File /usr/lib/python2.7/random.py, line 274, in choice return seq[int(self.random() * len(seq))] # raises IndexError if seq is empty ValueError: cannot convert float NaN to integer I have tried a purge and install but it doesn't fix this. No idea how to work around this. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sun Oct 7 18:43:46 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-10-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1063350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1063350] Re: curl corrupts floating point context
Right, I meant that I can no longer reproduce the problem on 14.10. It could be because I don't have the right hardware anymore to trigger it, but I think it's more likely that something in the Utopic stack has essentially fixed the problem. Any, for others who many stumble upon this bug in the future, please reopen it if you can still reproduce it in 14.10 or later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1063350 Title: curl corrupts floating point context Status in “pycurl” package in Ubuntu: Incomplete Status in “pycurl” source package in Precise: New Status in “pycurl” source package in Trusty: Incomplete Status in “pycurl” source package in Utopic: Incomplete Bug description: # add-apt-repository ppa:ubuntu-wine/ppa You are about to add the following PPA to your system: Welcome to the Wine Team PPA. Here you can get the latest available Wine betas for every supported version of Ubuntu. This PPA is managed by Scott Ritchie and Maarten Lankhorst. More info: https://launchpad.net/~ubuntu-wine/+archive/ppa Press [ENTER] to continue or ctrl-c to cancel adding it Exception in thread Thread-1: Traceback (most recent call last): File /usr/lib/python2.7/threading.py, line 551, in __bootstrap_inner self.run() File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 99, in run self.add_ppa_signing_key(self.ppa_path) File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 132, in add_ppa_signing_key tmp_keyring_dir = tempfile.mkdtemp() File /usr/lib/python2.7/tempfile.py, line 322, in mkdtemp name = names.next() File /usr/lib/python2.7/tempfile.py, line 141, in next letters = [choose(c) for dummy in 123456] File /usr/lib/python2.7/random.py, line 274, in choice return seq[int(self.random() * len(seq))] # raises IndexError if seq is empty ValueError: cannot convert float NaN to integer I have tried a purge and install but it doesn't fix this. No idea how to work around this. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sun Oct 7 18:43:46 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-10-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1063350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383539] Re: phased update support does not give idempotent answer for each (machine, update)
** Also affects: ubuntu-system-image
Importance: Undecided
Status: New
** No longer affects: system-image (Ubuntu)
** Changed in: ubuntu-system-image
Assignee: (unassigned) = Barry Warsaw (barry)
** Changed in: ubuntu-system-image
Importance: Undecided = High
** Changed in: ubuntu-system-image
Milestone: None = 2.5.1
** Changed in: ubuntu-system-image
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1383539
Title:
phased update support does not give idempotent answer for each
(machine,update)
Status in Ubuntu system image (server/client/updater):
Triaged
Bug description:
The phased update implementation in ./systemimage/helpers.py does:
def phased_percentage(*, reset=False):
global _pp_cache
if _pp_cache is None:
with open(UNIQUE_MACHINE_ID_FILE, 'rb') as fp:
data = fp.read()
now = str(time.time()).encode('us-ascii')
r = random.Random()
r.seed(data + now)
_pp_cache = r.randint(0, 100)
try:
return _pp_cache
finally:
if reset:
_pp_cache = None
Since the current time is used as a seed, this function will return a
different value each time it's called.
The phased update model requires that, for each given machine and each
given update, the calculated percentage persists. With this
implementation, since the seed is different for each invocation and
the result is not cached, phasing will happen much more quickly than
intended.
system-image should avoid using the time as a seed, and instead use a
predictable (but well-distributed) seed of the machine ID plus an
image identifier (perhaps full channel name + image ID).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-image/+bug/1383539/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon
This has only been a cosmetic bug for me for a long time. However, I took the ping as an opportunity to try a few of the things in comment #6. Changing managed=false to managed=true was the only change necessary to fix the icon in Utopic. I consider this bug fixed. ** Changed in: network-manager (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/751939 Title: Wired-only machine has empty volcano icon Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/751939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon
** Changed in: network-manager (Ubuntu) Status: Fix Released = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/751939 Title: Wired-only machine has empty volcano icon Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/751939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 751939] Re: Wired-only machine has empty volcano icon
I take that back. Setting managed=true breaks the networking. Even though I get the proper icon and all the network connection information appears to be correct (both as displayed by ifconfig and through the NM u/i), I cannot ping or connect to any service outside my LAN. Gateway and DNS services, IPv4 address and netmask all *look* right, but nothing gets outside the LAN. Setting it back to managed=false fixes this but of course volcano-izes the icon. I'll take functional networking over cosmetics. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/751939 Title: Wired-only machine has empty volcano icon Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/751939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1341685] Re: When unconstrained, udm sometimes downloads files to wrong location
On Oct 28, 2014, at 03:49 PM, Olli Ries wrote:
please fix after RTM via OTA
Shouldn't this be fixed for RTM?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubuntu.
https://bugs.launchpad.net/bugs/1341685
Title:
When unconstrained, udm sometimes downloads files to wrong location
Status in Ubuntu Download Manager:
In Progress
Status in “ubuntu-download-manager” package in Ubuntu:
In Progress
Status in “ubuntu-download-manager” package in Ubuntu RTM:
In Progress
Bug description:
I'm working on making the s-i tests more robust and I've run into an
odd situation, where udm sometimes stores its downloaded files using
an incorrect path, and not the one that s-i (which is unconstrained)
requests. This only appears to happen when the full s-i test suite is
run. When run in isolation, the test succeeds.
Here's a log of the createDownloadGroup call I'm making:
createDownloadGroup:
[Record(url='https://localhost:8943/gpg/blacklist.tar.xz',
destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz',
checksum=''),
Record(url='https://localhost:8943/gpg/blacklist.tar.xz.asc',
destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz.asc',
checksum='')]
url is the source url, destination is the local path to save the file
in. This call produces incorrect destination paths in the 'finished'
signal:
FINISHED: dbus.Array([dbus.String('/home/barry/.local/share/ubuntu-
download-manager//usr/lib/telepathy/mission-
control-5/Downloads/blacklist (20).tar.xz'),
dbus.String('/home/barry/.local/share/ubuntu-download-
manager//usr/lib/telepathy/mission-control-5/Downloads/blacklist
(20).tar.xz.asc')], signature=dbus.Signature('s'))
Notice the very strange directory udm chooses which is definitely not
the path requested, and in fact doesn't exist. This matches the
observed behavior that after a succesful group download completion
(i.e. no errors occur), I assert that the requested destination path
exists, and in the failing test it does not.
I suspect some state is not getting reset in udm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-download-manager/+bug/1341685/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1276347] Re: Some files are never downloaded (while under test)
*** This bug is a duplicate of bug 1329681 *** https://bugs.launchpad.net/bugs/1329681 I duped this to LP: #1329681 which we'll use to track general timeouts in udm. ** This bug has been marked a duplicate of bug 1329681 Sometimes Check for updates times out -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1276347 Title: Some files are never downloaded (while under test) Status in “ubuntu-download-manager” package in Ubuntu: New Bug description: I'm trying to debug the intermittent timeout errors I'm seeing in s-i when integrated with u-d-m. A TimeoutError means that s-i does not see the 'finished' signal in response to a successful group download (of course, a canceled or error signal would also terminate the s-i client reactor, but I don't see those either). I added some debugging to my test http/https server to log the requests. Using this set up I captured the output during one of the timed out tests, and what I saw was this (excerpt): 127.0.0.1 - - [04/Feb/2014 16:33:28] GET /stable/nexus7/index.json HTTP/1.1 200 - 127.0.0.1 - - [04/Feb/2014 16:33:28] GET /stable/nexus7/index.json.asc HTTP/1.1 200 - 127.0.0.1 - - [04/Feb/2014 16:33:28] GET /3/4/5.txt HTTP/1.1 200 - 127.0.0.1 - - [04/Feb/2014 16:33:28] GET /3/4/5.txt.asc HTTP/1.1 200 - 127.0.0.1 - - [04/Feb/2014 16:33:28] GET /4/5/6.txt HTTP/1.1 200 - 127.0.0.1 - - [04/Feb/2014 16:33:28] GET /4/5/6.txt.asc HTTP/1.1 200 - 127.0.0.1 - - [04/Feb/2014 16:33:28] GET /5/6/7.txt HTTP/1.1 200 - ERROR What's interesting about this is that I expected /5/6/7.txt.asc to also be downloaded, but it never was. IOW, the GET for 7.txt.asc was never seen by the http server. This leads me to think that something is happening to cause u-d-m to not process the entire group download, or to hang before it requests 7.txt.asc. If it were hanging or not completing the group download, then it would make sense that s-i would never see the 'finished' signal that would terminate the reactor. Unfortunately, due to previously reported bugs, it's nearly impossible to directly correlate this output with u-d-m output so that I can tell what u-d-m is doing while the s-i http server is expected to see one more file download. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1276347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373467] Re: Ability to specify alternate client.ini
** Also affects: ubuntu-system-image Importance: Undecided Status: New ** No longer affects: system-image (Ubuntu) ** Tags added: client ** Changed in: ubuntu-system-image Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1373467 Title: Ability to specify alternate client.ini Status in Ubuntu system image (server/client/updater): Triaged Bug description: Currently, the system-image package requires system-image-common. The latter provides /etc/system-image/client.ini which is configurated for a Touch environment. However, to allow system-image to be used on systems other than Touch, it would be useful to have the ability to specify an alternate client.ini. Maybe splitting client.ini out of system-image-common into its own package which could provide /etc/system-image/client.conf.d/touch.conf or similar? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1373467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348275] Re: gdb message Got object file from memory but can't read symbols: File truncated.
This is likely the cause of the upstream Python test suite failures.
** Bug watch added: Python Roundup #22327
http://bugs.python.org/issue22327
** Also affects: python via
http://bugs.python.org/issue22327
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1348275
Title:
gdb message Got object file from memory but can't read symbols: File
truncated.
Status in Python:
Unknown
Status in “gdb” package in Ubuntu:
Confirmed
Bug description:
$ cat foo.cEOT
#include stdio.h
#include stdlib.h
int
main (int argc, char *argv[])
{
printf (hello world\n);
exit (EXIT_SUCCESS);
}
EOT
$ gcc -ggdb -O0 foo.c
$ ./a.out
hello world
$ gdb ./a.out
GNU gdb (Ubuntu 7.7.91.20140723-0ubuntu1) 7.7.91.20140723-cvs
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from ./a.out...done.
(gdb) r
Starting program: /tmp/a.out
Got object file from memory but can't read symbols: File truncated.
# XXX: What is this? XXX:
hello world
[Inferior 1 (process 21518) exited normally]
(gdb)
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gdb 7.7.91.20140723-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
Uname: Linux 3.16.0-5-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 24 17:55:11 2014
InstallationDate: Installed on 2014-04-11 (103 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: gdb
UpgradeStatus: Upgraded to utopic on 2014-05-08 (77 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1348275/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1063350] Re: curl corrupts floating point context
I'm now working on pycurl 7.19.5 for Debian and I was looking at porting over as much of the Ubuntu delta as possible. I think the patch for this is no longer necessary, but it's difficult for me to test because I also no longer have an i386 machine on which to test. Note though that we are now linking against gnutls 2.8, so if the suspicion is that the bug is in gnutls 2.6, maybe it's fixed in 2.8 and pycurl won't be subject to the bug. In any case, I am not going to back port this fix, so we'll have to see if anybody reports a bug once the package is pulled into Ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1063350 Title: curl corrupts floating point context Status in “pycurl” package in Ubuntu: Triaged Bug description: # add-apt-repository ppa:ubuntu-wine/ppa You are about to add the following PPA to your system: Welcome to the Wine Team PPA. Here you can get the latest available Wine betas for every supported version of Ubuntu. This PPA is managed by Scott Ritchie and Maarten Lankhorst. More info: https://launchpad.net/~ubuntu-wine/+archive/ppa Press [ENTER] to continue or ctrl-c to cancel adding it Exception in thread Thread-1: Traceback (most recent call last): File /usr/lib/python2.7/threading.py, line 551, in __bootstrap_inner self.run() File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 99, in run self.add_ppa_signing_key(self.ppa_path) File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 132, in add_ppa_signing_key tmp_keyring_dir = tempfile.mkdtemp() File /usr/lib/python2.7/tempfile.py, line 322, in mkdtemp name = names.next() File /usr/lib/python2.7/tempfile.py, line 141, in next letters = [choose(c) for dummy in 123456] File /usr/lib/python2.7/random.py, line 274, in choice return seq[int(self.random() * len(seq))] # raises IndexError if seq is empty ValueError: cannot convert float NaN to integer I have tried a purge and install but it doesn't fix this. No idea how to work around this. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sun Oct 7 18:43:46 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-10-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1063350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1063350] Re: curl corrupts floating point context
I've verified this patch is no longer necessary with pycurl 7.19.5, which I will FFe shortly into Utopic. It could be building it against gnutls28, or changes in pycurl itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1063350 Title: curl corrupts floating point context Status in “pycurl” package in Ubuntu: Triaged Bug description: # add-apt-repository ppa:ubuntu-wine/ppa You are about to add the following PPA to your system: Welcome to the Wine Team PPA. Here you can get the latest available Wine betas for every supported version of Ubuntu. This PPA is managed by Scott Ritchie and Maarten Lankhorst. More info: https://launchpad.net/~ubuntu-wine/+archive/ppa Press [ENTER] to continue or ctrl-c to cancel adding it Exception in thread Thread-1: Traceback (most recent call last): File /usr/lib/python2.7/threading.py, line 551, in __bootstrap_inner self.run() File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 99, in run self.add_ppa_signing_key(self.ppa_path) File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 132, in add_ppa_signing_key tmp_keyring_dir = tempfile.mkdtemp() File /usr/lib/python2.7/tempfile.py, line 322, in mkdtemp name = names.next() File /usr/lib/python2.7/tempfile.py, line 141, in next letters = [choose(c) for dummy in 123456] File /usr/lib/python2.7/random.py, line 274, in choice return seq[int(self.random() * len(seq))] # raises IndexError if seq is empty ValueError: cannot convert float NaN to integer I have tried a purge and install but it doesn't fix this. No idea how to work around this. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sun Oct 7 18:43:46 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-10-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1063350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376736] [NEW] [FFe] update to pycurl 7.19.5
Public bug reported: I recently uploaded 7.19.5-2 to unstable. This version fixes several Debian reported bugs and also merges in the still-relevant Ubuntu deltas. We'll need to continue to carry a delta for the cross-pocket build-deps, but these won't affect the functionality of the package. This version also re-syncs the Debian vcs with the NMU that was done by an non-team developer. I've confirmed the new version fixes LP: #1063350 since afaict there is no longer any floating point corruptions (even dropping the Ubuntu delta). The new version also fixes a bug that is relevant to system-image. From the upstream changelog: * When passing a file-like object to READDATA option, PycURL was mistakenly looking for write method on this object. Now read method is looked up, as would be expected. http://pycurl.sourceforge.net/ChangeLog I've verified that a 7.19.5-2ubuntu1 builds and runs on Utopic. I've tested it against the LP: #1063350 test case on physical i386 hardware and it does not exhibit the floating point corruption. ** Affects: pycurl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1376736 Title: [FFe] update to pycurl 7.19.5 Status in “pycurl” package in Ubuntu: New Bug description: I recently uploaded 7.19.5-2 to unstable. This version fixes several Debian reported bugs and also merges in the still-relevant Ubuntu deltas. We'll need to continue to carry a delta for the cross-pocket build-deps, but these won't affect the functionality of the package. This version also re-syncs the Debian vcs with the NMU that was done by an non-team developer. I've confirmed the new version fixes LP: #1063350 since afaict there is no longer any floating point corruptions (even dropping the Ubuntu delta). The new version also fixes a bug that is relevant to system-image. From the upstream changelog: * When passing a file-like object to READDATA option, PycURL was mistakenly looking for write method on this object. Now read method is looked up, as would be expected. http://pycurl.sourceforge.net/ChangeLog I've verified that a 7.19.5-2ubuntu1 builds and runs on Utopic. I've tested it against the LP: #1063350 test case on physical i386 hardware and it does not exhibit the floating point corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1376736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1063350] Re: curl corrupts floating point context
** Changed in: pycurl (Ubuntu) Status: Triaged = Incomplete ** Also affects: pycurl (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: pycurl (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: pycurl (Ubuntu Utopic) Importance: Medium Assignee: Barry Warsaw (barry) Status: Incomplete ** Changed in: pycurl (Ubuntu Trusty) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1063350 Title: curl corrupts floating point context Status in “pycurl” package in Ubuntu: Incomplete Status in “pycurl” source package in Precise: New Status in “pycurl” source package in Trusty: Incomplete Status in “pycurl” source package in Utopic: Incomplete Bug description: # add-apt-repository ppa:ubuntu-wine/ppa You are about to add the following PPA to your system: Welcome to the Wine Team PPA. Here you can get the latest available Wine betas for every supported version of Ubuntu. This PPA is managed by Scott Ritchie and Maarten Lankhorst. More info: https://launchpad.net/~ubuntu-wine/+archive/ppa Press [ENTER] to continue or ctrl-c to cancel adding it Exception in thread Thread-1: Traceback (most recent call last): File /usr/lib/python2.7/threading.py, line 551, in __bootstrap_inner self.run() File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 99, in run self.add_ppa_signing_key(self.ppa_path) File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 132, in add_ppa_signing_key tmp_keyring_dir = tempfile.mkdtemp() File /usr/lib/python2.7/tempfile.py, line 322, in mkdtemp name = names.next() File /usr/lib/python2.7/tempfile.py, line 141, in next letters = [choose(c) for dummy in 123456] File /usr/lib/python2.7/random.py, line 274, in choice return seq[int(self.random() * len(seq))] # raises IndexError if seq is empty ValueError: cannot convert float NaN to integer I have tried a purge and install but it doesn't fix this. No idea how to work around this. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sun Oct 7 18:43:46 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-10-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1063350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 982436] Re: can not import pycurl: librtmp.so.0: cannot open shared object file: No such file or directory
Has anybody noticed this problem on 14.04 or 14.10? Seems like there's been no additional comments in over a year and I suspect the newer versions of pycurl do not suffer this problem. ** Also affects: pycurl (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: pycurl (Ubuntu Utopic) Importance: Medium Status: Confirmed ** Also affects: pycurl (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: pycurl (Ubuntu Utopic) Status: Confirmed = Incomplete ** Changed in: pycurl (Ubuntu Trusty) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/982436 Title: can not import pycurl: librtmp.so.0: cannot open shared object file: No such file or directory Status in “pycurl” package in Ubuntu: Incomplete Status in “pycurl” source package in Precise: New Status in “pycurl” source package in Trusty: Incomplete Status in “pycurl” source package in Utopic: Incomplete Bug description: when I typed this in teminal, there showed report window with this sentence ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 ApportVersion: 2.0.1-0ubuntu3 Architecture: i386 Date: Sun Apr 15 18:28:41 2012 ExecutablePath: /usr/bin/add-apt-repository InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/add-apt-repository ppa:webupd8team/gnome3 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 LANGUAGE=en_US:en SHELL=/bin/bash PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:webupd8team/gnome3'] SourcePackage: software-properties Title: add-apt-repository crashed with ImportError in /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py: librtmp.so.0: cannot open shared object file: No such file or directory UpgradeStatus: Upgraded to precise on 2012-04-06 (9 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/982436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 497949] Re: pycurl contents missing
This bug is quite old. Is it still a problem in newer versions of Ubuntu? ** Changed in: pycurl (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/497949 Title: pycurl contents missing Status in “pycurl” package in Ubuntu: Incomplete Bug description: When i try to use package manager for installing / un-installing of any software, it keeps failing with following progress: I couldn't find a solution for this. What could be the problem please? Thanks peter@peterk:~$ sudo apt-get install vlc Reading package lists... Done Building dependency tree Reading state information... Done vlc is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 18 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up python-pycurl (7.18.2-1build1) ... /var/lib/dpkg/info/python-pycurl.postinst: 14: pycentral: not found dpkg: error processing python-pycurl (--configure): subprocess post-installation script returned error exit status 127 Setting up python-pexpect (2.1-1build1) ... /var/lib/dpkg/info/python-pexpect.postinst: 9: pycentral: not found dpkg: error processing python-pexpect (--configure): subprocess post-installation script returned error exit status 127 dpkg: dependency problems prevent configuration of python-smartpm: python-smartpm depends on python-pycurl; however: Package python-pycurl is not configured yet. python-smartpm depends on python-pexpect; however: Package python-pexpect is not configured yet. dpkg: error processing python-smartpm (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of landscape-common: landscape-common depends on python-smartpm (= 1.1.1~bzr20081010-0ubuntu1); however: Package python-smartpm is not configured yet. dpkg: error processing landscape-common (--configure): dependency problems - leaving unconfigured Setting up linux-image-2.6.27-15-generic (2.6.27-15.43) ... No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because MaxReports is reached already Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.27-15-generic Running postinst hook script /sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.27-16-generic Found kernel: /boot/vmlinuz-2.6.27-15-generic Found kernel: /boot/vmlinuz-2.6.27-14-generic Found kernel: /boot/vmlinuz-2.6.27-11-generic Found kernel: /boot/vmlinuz-2.6.27-9-generic Found kernel: /boot/vmlinuz-2.6.27-7-generic Found kernel: /boot/vmlinuz-2.6.24-21-generic Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/nvidia-common /etc/kernel/postinst.d/nvidia-common: /usr/bin/nvidia-detector: /usr/bin/python: bad interpreter: No such file or directory run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 126 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.27-15-generic.postinst line 1002. dpkg: error processing linux-image-2.6.27-15-generic (--configure): subprocess post-installation script returned error exit status 2 No apport report written because MaxReports is reached already Setting up linux-image-2.6.27-16-generic (2.6.27-16.44) ... Running depmod. update-initramfs: Generating /boot/initrd.img-2.6.27-16-generic Running postinst hook script /sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.27-16-generic Found kernel: /boot/vmlinuz-2.6.27-15-generic Found kernel: /boot/vmlinuz-2.6.27-14-generic Found kernel: /boot/vmlinuz-2.6.27-11-generic Found kernel: /boot/vmlinuz-2.6.27-9-generic Found kernel: /boot/vmlinuz-2.6.27-7-generic Found kernel: /boot/vmlinuz-2.6.24-21-generic Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/nvidia-common /etc/kernel/postinst.d/nvidia-common: /usr/bin/nvidia-detector: /usr/bin/python: bad interpreter: No such file or
[Touch-packages] [Bug 1075642] Re: package python-pycurl 7.19.0-4ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 101
This bug is quite old, with no additional affected people or information. Is it still a problem in newer versions of Ubuntu? ** Changed in: pycurl (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1075642 Title: package python-pycurl 7.19.0-4ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 101 Status in “pycurl” package in Ubuntu: Incomplete Bug description: Upgrade from 10.04 to 12.04 ProblemType: Package DistroRelease: Ubuntu 12.04 Package: python-pycurl ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 6 10:51:30 2012 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 101 SourcePackage: pycurl Title: package python-pycurl 7.19.0-4ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 101 UpgradeStatus: Upgraded to precise on 2012-11-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1075642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 364186] Re: Documentation is not XHTML
This should be long fixed upstream by now. ** Changed in: pycurl (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/364186 Title: Documentation is not XHTML Status in PycURL - Python interface to cURL: Unknown Status in “pycurl” package in Ubuntu: Fix Released Bug description: Binary package hint: python-pycurl The page /usr/share/doc/python-pycurl/html/curlshareobject.html has a nice XHTML 1.0 compliancy image at the bottom, but it fails to parse as XML. In Opera, I get a message, and xmllint reports errors: /usr/share/doc/python-pycurl/html/curlshareobject.html:40: parser error : Opening and ending tag mismatch: p line 20 and dd /dd ^ (and so on). To manage notifications about this bug go to: https://bugs.launchpad.net/pycurl/+bug/364186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1086667] Re: Wrong documentation URL in help(curl)
Hmm, help(curl) for me doesn't even have a MODULE DOCS section, and there's nothing clickable. ** Changed in: pycurl (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1086667 Title: Wrong documentation URL in help(curl) Status in “pycurl” package in Ubuntu: Incomplete Bug description: Ubuntu 12.04.1 LTSpython-pycurl-7.19.0-4ubuntu3 Wrong documentation URL in help(curl) Steps to reproduce: 1. Open Terminal, run python 2. in python's console import curl help(curl) 3. Click to 'MODULE DOCS' URL (currently it is http://docs.python.org/library/curl ) Actual result: Not Found The requested URL /2/library/curl was not found on this server. Apache/2.2.16 (Debian) Server at docs.python.org Port 80 Expected result: Documentation on 'curl' module will opens in browser's window (URL must be available and with right content). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-pycurl 7.19.0-4ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31 Uname: Linux 3.2.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Wed Dec 5 12:40:09 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pycurl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1086667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1111673] Re: pycurl built with gnutls not working as openssl (error: gnutls_handshake() failed)
** Bug watch added: Debian Bug tracker #515200 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515200 ** Also affects: pycurl (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515200 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/673 Title: pycurl built with gnutls not working as openssl (error: gnutls_handshake() failed) Status in “pycurl” package in Ubuntu: Confirmed Status in “pycurl” package in Debian: Unknown Bug description: A call to that lib returns problem in gnutls_handshake(). The problem is that pycurl was built with gnutls. Building it with openssl the problem disappear. Below there is a 'how to' to build with openssl, replacing some calls to gnutls with calls to openssl. Details: I'm trying to use 'git' and a server set up with apache+SSL. When I try to clone a repository I get the following error: Cloning into 'test.git'... error: gnutls_handshake() failed: A TLS warning alert has been received. while accessing https://my server/test.git/info/refs fatal: HTTP request failed Looking for some information I've found this bug on Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515200 And, looking a bit more, I've found a solution that works for me: https://code.google.com/p/wfuzz/wiki/PyCurlSSLBug Is it possible to have a different version of python-pycurl compiled with openssl? Thanks! ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: python-pycurl 7.19.0-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Thu Jan 31 15:53:40 2013 InstallationDate: Installed on 2012-12-03 (59 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pycurl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1111673] Re: pycurl built with gnutls not working as openssl (error: gnutls_handshake() failed)
I can no longer verify this bug with the latest versions of pycurl in Debian (7.19.5-2) built against gnutls28. See the Debian bug for details. I have an Ubuntu version that is awaiting FFe for upload to utopic and it also does not exhibit this problem. If you still see the problem in Utopic after the upload of the new version, please reopen this bug. ** Changed in: pycurl (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/673 Title: pycurl built with gnutls not working as openssl (error: gnutls_handshake() failed) Status in “pycurl” package in Ubuntu: Invalid Status in “pycurl” package in Debian: Unknown Bug description: A call to that lib returns problem in gnutls_handshake(). The problem is that pycurl was built with gnutls. Building it with openssl the problem disappear. Below there is a 'how to' to build with openssl, replacing some calls to gnutls with calls to openssl. Details: I'm trying to use 'git' and a server set up with apache+SSL. When I try to clone a repository I get the following error: Cloning into 'test.git'... error: gnutls_handshake() failed: A TLS warning alert has been received. while accessing https://my server/test.git/info/refs fatal: HTTP request failed Looking for some information I've found this bug on Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515200 And, looking a bit more, I've found a solution that works for me: https://code.google.com/p/wfuzz/wiki/PyCurlSSLBug Is it possible to have a different version of python-pycurl compiled with openssl? Thanks! ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: python-pycurl 7.19.0-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Thu Jan 31 15:53:40 2013 InstallationDate: Installed on 2012-12-03 (59 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pycurl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333672] Re: Tests fail and do not fail the package build
I have 7.19.5-2ubuntu1 ready to go into Utopic as soon as the FFE is approved (LP: #1376736). Unfortunately, due to an upstream packaging bug, the test suite was not included in the tarball, and I elected not to re-add it in the Debian version (7.19.5-2). My plan is to re-enable it once upstream releases a new version, and exactly as you state, add a DEP-8 test that runs the test suite. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1333672 Title: Tests fail and do not fail the package build Status in “pycurl” package in Ubuntu: New Bug description: pycurl is in main, so is expected to meet https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, including If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build. pycurl currently (7.19.3-0ubuntu3) does have a test suite that does run during the build, but the test suite fails and this does not fail the build. pycurl now depends on python-bottle, which is in universe, but it could still have a dep8 test that runs this test suite. However, even with python-bottle installed, not all tests pass. That's as far as I got during a pycurl merge, so I'll leave this bug here for another time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1333672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365746] Re: Some URLS produce gnutls_handshake() failed: Illegal parameter error, but others do not
I've tested all of these urls against pycurl 7.19.5-2ubuntu1 which should be uploaded to Utopic as soon as the FFE is approved. None of them have any trouble. If you notice the problem again when the new version is available, please re-open this bug. ** Changed in: pycurl (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1365746 Title: Some URLS produce gnutls_handshake() failed: Illegal parameter error, but others do not Status in “pycurl” package in Ubuntu: Incomplete Bug description: #I wrote a script that can turn on and off the crashing behavior of gnutls. Hopefully this will help someone debug it. Using curl #from the command line on the same machine fetches the URL's okay, so it seems like a pycurl thing... Many thanks to the devs! #!/usr/bin/python import pycurl c = pycurl.Curl() # Uncomment this one and it will crash gnutls #c.setopt(c.URL, 'https://mobile.tdameritrade.com/wireless/landingProspectAction.action') # Uncomment this one and it will crash gnutls c.setopt(c.URL, 'https://invest.ameritrade.com/grid/m/login') # This url will work if you uncomment it #c.setopt(c.URL, 'https://www.discovercard.com/cardmembersvcs/mobile/app/loginlogout/auth') print(About to go to TDAmeritrade (and crash)) c.perform() #curl 7.35.0 (x86_64-pc-linux-gnu) libcurl/7.35.0 OpenSSL/1.0.1f zlib/1.2.8 libidn/1.28 librtmp/2.3 #Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smtp smtps telnet tftp #Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP #python-pycurl version 7.19.3-0ubuntu # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1365746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376758] Re: Ability to specify script to call at end of download rather than rebooting
We have a [hooks]reboot setting in client.ini. The way to address this would be to add an appropriate implementation in a separate callable, and then point client.ini to this alternate implementation. ** Tags added: client ** Also affects: ubuntu-system-image Importance: Undecided Status: New ** No longer affects: system-image (Ubuntu) ** Changed in: ubuntu-system-image Milestone: None = 3.0 ** Changed in: ubuntu-system-image Status: New = Triaged ** Changed in: ubuntu-system-image Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1376758 Title: Ability to specify script to call at end of download rather than rebooting Status in Ubuntu system image (server/client/updater): Triaged Bug description: Currently, after downloading the latest image, system-image-cli reboots the system. It would be extremely useful if rather than hard-coding this, system- image-cli could conditionally call a hook script when it has finished. Ideally, it would be possible to specify this in /etc/system- image/client.ini Since the desired behaviour could well be device/environment specific, maybe the reboot ability should also be pulled out of systemimage/reboot.py so that by default, /etc/system- image/hooks/default - /etc/system-image/hooks/reboot.sh gets run, but that could be overriden via client.ini. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1376758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333672] Re: Tests fail and do not fail the package build
** Bug watch added: Debian Bug tracker #763770 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763770 ** Also affects: pycurl (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763770 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1333672 Title: Tests fail and do not fail the package build Status in “pycurl” package in Ubuntu: Triaged Status in “pycurl” package in Debian: Unknown Bug description: pycurl is in main, so is expected to meet https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, including If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build. pycurl currently (7.19.3-0ubuntu3) does have a test suite that does run during the build, but the test suite fails and this does not fail the build. pycurl now depends on python-bottle, which is in universe, but it could still have a dep8 test that runs this test suite. However, even with python-bottle installed, not all tests pass. That's as far as I got during a pycurl merge, so I'll leave this bug here for another time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1333672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333672] Re: Tests fail and do not fail the package build
** Changed in: pycurl (Ubuntu) Status: New = Triaged ** Changed in: pycurl (Ubuntu) Importance: Undecided = Medium ** Changed in: pycurl (Ubuntu) Assignee: (unassigned) = Barry Warsaw (barry) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1333672 Title: Tests fail and do not fail the package build Status in “pycurl” package in Ubuntu: Triaged Status in “pycurl” package in Debian: Unknown Bug description: pycurl is in main, so is expected to meet https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, including If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build. pycurl currently (7.19.3-0ubuntu3) does have a test suite that does run during the build, but the test suite fails and this does not fail the build. pycurl now depends on python-bottle, which is in universe, but it could still have a dep8 test that runs this test suite. However, even with python-bottle installed, not all tests pass. That's as far as I got during a pycurl merge, so I'll leave this bug here for another time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1333672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376736] Re: [FFe] update to pycurl 7.19.5
** Changed in: pycurl (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1376736 Title: [FFe] update to pycurl 7.19.5 Status in “pycurl” package in Ubuntu: New Bug description: I recently uploaded 7.19.5-2 to unstable. This version fixes several Debian reported bugs and also merges in the still-relevant Ubuntu deltas. We'll need to continue to carry a delta for the cross-pocket build-deps, but these won't affect the functionality of the package. This version also re-syncs the Debian vcs with the NMU that was done by an non-team developer. I've confirmed the new version fixes LP: #1063350 since afaict there is no longer any floating point corruptions (even dropping the Ubuntu delta). The new version also fixes a bug that is relevant to system-image. From the upstream changelog: * When passing a file-like object to READDATA option, PycURL was mistakenly looking for write method on this object. Now read method is looked up, as would be expected. http://pycurl.sourceforge.net/ChangeLog I've verified that a 7.19.5-2ubuntu1 builds and runs on Utopic. I've tested it against the LP: #1063350 test case on physical i386 hardware and it does not exhibit the floating point corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1376736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333672] Re: Tests fail and do not fail the package build
** Changed in: pycurl (Ubuntu) Importance: Medium = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1333672 Title: Tests fail and do not fail the package build Status in “pycurl” package in Ubuntu: Triaged Status in “pycurl” package in Debian: Unknown Bug description: pycurl is in main, so is expected to meet https://wiki.ubuntu.com/UbuntuMainInclusionRequirements, including If the package ships a test suite, and there is no obvious reason why it cannot work during build (e. g. it needs root privileges or network access), it should be run during package build, and a failing test suite should fail the build. pycurl currently (7.19.3-0ubuntu3) does have a test suite that does run during the build, but the test suite fails and this does not fail the build. pycurl now depends on python-bottle, which is in universe, but it could still have a dep8 test that runs this test suite. However, even with python-bottle installed, not all tests pass. That's as far as I got during a pycurl merge, so I'll leave this bug here for another time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1333672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1176944] Re: pycurl.TIMEOUT_MS not work when the value = 999
I just tested this with pycurl 7.19.5 (hopefully soon uploaded to Utopic). It seems to work for me. For example, if I bump the timeout down to 100ms (since baidu comes back quicker than 999ms for me), I see the timeout regardless of whether NOSIGNAL is set or not. So I guess this is fixed in newer versions of pycurl. ** Changed in: pycurl (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1176944 Title: pycurl.TIMEOUT_MS not work when the value = 999 Status in “pycurl” package in Ubuntu: Incomplete Bug description: At first, I'm sorry if this is not a bug or here is not the right place to report... ===Code Sample= import time import pycurl c = pycurl.Curl() c.setopt(pycurl.URL, 'http://baidu.com/') start = time.time() c.setopt(pycurl.TIMEOUT_MS, 999) try: c.perform() except: print Timeout finally: print time.time() - start c = pycurl.Curl() c.setopt(pycurl.URL, 'http://baidu.com/') c.setopt(pycurl.TIMEOUT_MS, 999) c.setopt(pycurl.NOSIGNAL, 1) c.perform() print set NOSIGNAL makes it work OutPut== Timeout 0.0002281665802 html meta http-equiv=refresh content=0;url=http://www.baidu.com/; /html set NOSIGNAL makes it work = system: quantal python-pycurl version: 7.19.0-5ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1176944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377184] Re: move archive_master file out of /etc to avoid it being treated as a conffile
** Also affects: ubuntu-system-image Importance: Undecided Status: New ** Changed in: ubuntu-system-image Milestone: None = 3.0 ** Changed in: ubuntu-system-image Status: New = Triaged ** Changed in: ubuntu-system-image Importance: Undecided = High ** Changed in: ubuntu-system-image Assignee: (unassigned) = Barry Warsaw (barry) ** No longer affects: system-image (Ubuntu) ** Tags added: client -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1377184 Title: move archive_master file out of /etc to avoid it being treated as a conffile Status in Ubuntu system image (server/client/updater): Triaged Bug description: Currently client.ini specifies: [gpg] archive_master: /etc/system-image/archive-master.tar.xz The problem is that file in /etc are automatically marked as conffiles by debhelper and as such don't get moved into place until the dpkg configure step. This caused an issue for the initramfs-tools-ubuntu-core package since that Depends on system-image-common (which provides etc/system-image/archive-master.tar.xz), but when the initramfs-tools-ubuntu-core package was unpacked, this triggered update-initramfs which failed since it needs access to /etc/system-image/archive-master.tar.xz, but that file had not yet been moved into place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1377184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377956] Re: modify semantics of bootme attribute to support delayed reboot
** Also affects: ubuntu-system-image Importance: Undecided Status: New ** No longer affects: system-image (Ubuntu) ** Tags added: client ** Changed in: ubuntu-system-image Status: New = Triaged ** Changed in: ubuntu-system-image Milestone: None = 3.0 ** Changed in: ubuntu-system-image Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1377956 Title: modify semantics of bootme attribute to support delayed reboot Status in Ubuntu system image (server/client/updater): Triaged Bug description: system-image currently supports a 'bootme' option that may be present in the JSON and instructs Touch to reboot _after it has finished downloading the current file_. However, Core has a slightly different requirement. It attempts to minimise reboots, but when certain packages (like the kernel) have been updated, a reboot will be required. Crucially though, this reboot should not occur until the the system image has been fully downloaded *and* fully unpacked. After a discussion with barry+mvo, we think the best approach is to modify the bootme flag to be able to specify a 'deferred' value meaning reboot at end of download+unpack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1377956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376736] Re: [FFe] update to pycurl 7.19.5
** Changed in: pycurl (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1376736 Title: [FFe] update to pycurl 7.19.5 Status in “pycurl” package in Ubuntu: Fix Released Bug description: I recently uploaded 7.19.5-2 to unstable. This version fixes several Debian reported bugs and also merges in the still-relevant Ubuntu deltas. We'll need to continue to carry a delta for the cross-pocket build-deps, but these won't affect the functionality of the package. This version also re-syncs the Debian vcs with the NMU that was done by an non-team developer. I've confirmed the new version fixes LP: #1063350 since afaict there is no longer any floating point corruptions (even dropping the Ubuntu delta). The new version also fixes a bug that is relevant to system-image. From the upstream changelog: * When passing a file-like object to READDATA option, PycURL was mistakenly looking for write method on this object. Now read method is looked up, as would be expected. http://pycurl.sourceforge.net/ChangeLog I've verified that a 7.19.5-2ubuntu1 builds and runs on Utopic. I've tested it against the LP: #1063350 test case on physical i386 hardware and it does not exhibit the floating point corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1376736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387214] Re: file corruption on touch images in rw portions of the filesystem
If you want a separate fsck command in ubuntu_command, please file a separate bug on upstream system-image project. Other than that, it doesn't look like this particular bug affects system-image client. ** No longer affects: system-image (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in “android” package in Ubuntu: Triaged Status in “initramfs-tools-ubuntu-touch” package in Ubuntu: Triaged Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh The kernel team has verified the above reproducer and symptoms. Related bugs: * bug 1371771 * bug 1371765 * bug 1377338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1387214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391574] [NEW] Terminal keyboard shortcut problem
Public bug reported: Over in LP: #1391337 I reported a problem on vivid where Terminal wasn't displaying its menu bar underlines when you hold down Alt. This was perhaps caused by a problem in the switch from gconf to gsettings. I've turned on Terminal-Preferences-General-Enable mnemonics Now the menu bar underlines are there, but when I dive into the items of a menu, there are no underlines on the shortcuts until I hit down arrow. However, the shortcuts are available even before hitting down arrow. For example: Alt-t brings up the Terminal menu. Reset and Clear is bound to 'l' (el), but the 'l' in 'Clear' is not underlined. If I hit 'l' at this point, the operation works. If, after hitting Alt-t to bring up the Terminal menu I then hit down arrow, the underline in the 'l' in 'Clear' shows up. The menu item underlines should show up immediately when the menu items are displayed. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1391574 Title: Terminal keyboard shortcut problem Status in “unity” package in Ubuntu: New Bug description: Over in LP: #1391337 I reported a problem on vivid where Terminal wasn't displaying its menu bar underlines when you hold down Alt. This was perhaps caused by a problem in the switch from gconf to gsettings. I've turned on Terminal-Preferences-General-Enable mnemonics Now the menu bar underlines are there, but when I dive into the items of a menu, there are no underlines on the shortcuts until I hit down arrow. However, the shortcuts are available even before hitting down arrow. For example: Alt-t brings up the Terminal menu. Reset and Clear is bound to 'l' (el), but the 'l' in 'Clear' is not underlined. If I hit 'l' at this point, the operation works. If, after hitting Alt-t to bring up the Terminal menu I then hit down arrow, the underline in the 'l' in 'Clear' shows up. The menu item underlines should show up immediately when the menu items are displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1391574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391616] [NEW] Screen blanks after 10 minutes regardless of brightness setting
Public bug reported: I don't know whether this is a unity bug or elsewhere, but I'm noticing this problem after upgrading from utopic to vivid. On your desktop, go to System Settings - Brightness and Lock and set the turn screen off time to 1 hour. Wait 10 minutes without using your desktop, and the screen goes blank.However, even though Lock screen after is set to Screen turns off, the lock screen is not activated. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1391616 Title: Screen blanks after 10 minutes regardless of brightness setting Status in “unity” package in Ubuntu: New Bug description: I don't know whether this is a unity bug or elsewhere, but I'm noticing this problem after upgrading from utopic to vivid. On your desktop, go to System Settings - Brightness and Lock and set the turn screen off time to 1 hour. Wait 10 minutes without using your desktop, and the screen goes blank.However, even though Lock screen after is set to Screen turns off, the lock screen is not activated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1391616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
apt-mark lightdm hold apt-get dist-upgrade reboot
Indeed, logins are fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
Fix Committed
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
Hmm, as 1.13.0-0ubuntu1 just showed up in vivid, it broke my login in
the follow way. Note that I always try devel channel updates in a VM
with a snapshotted disk so I'm able to revert and do some further
investigating. Looking at the dist-upgrade packages, I suspect the
lightdm changes are affecting me, but I'm going to continue to
investigate.
So, when I log in, I do get several warnings in a dialog. Most are
because I use `source` instead of `.` to source other shell files. What
shell is lightdm using these days? Still, even with the warnings, I can
log in just fine.
Anyway, when I change them all to `.` I still get one warning about my
use of shopt, but I'll just ignore that for now. However, logins are
now completely broken. I see the screen blank and then I'm thrown back
to the login screen. ~/.xsession-errors is empty and I can find no
other log file either in $HOME or /var/log that contains any information
about what's going wrong.
I'm going to pin lightdm and dist-upgrade everything else just to verify
that the lightdm update is causing my problems. How can I debug the
login crash after I fix my login scripts?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
Fix Committed
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
For now I'll keep the hold on lightdm, but if Robert or someone else
wants to debug in real-time, ping me on irc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
Fix Committed
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
Hi Gunnar.
On Nov 14, 2014, at 07:07 PM, Gunnar Hjalmarsson wrote:
It has always been using Bourne shell, so source is not understood.
You have obliviously been running your system without the configuration
in those other shell files.
Sure, it's entirely possibly that my login has been silently ignoring the
non-sh syntax errors, so in that respect, getting notification of them now is
a good thing.
I still wonder what in my shell code could be causing lightdm to exit back
to the login screen and where those errors would be logged so that I can view
them and debug them.
Cheers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
Fix Committed
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
On Nov 14, 2014, at 08:15 PM, Gunnar Hjalmarsson wrote:
Being thrown back indicates a syntax error.
Are those errors logged anywhere permanently?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
Fix Committed
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
On Nov 14, 2014, at 09:59 PM, Gunnar Hjalmarsson wrote:
I don't know. Syntax errors directly in e.g. ~/.profile or /etc/profile
are logged in ~/.xsession-errors both with the latest lightdm version
and with previous versions, but I don't know whether syntax errors in
files which are sourced from those files are logged anywhere.
I guess they aren't because ~/.xsession-errors is empty when lightdm exits
back to the login screen. :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
Fix Committed
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
On Nov 14, 2014, at 11:38 PM, Gunnar Hjalmarsson wrote:
Right now I don't know how to best deal with this issue. Any advice
appreciated.
Probably use tee(1) to get the output both into the temp file and
~/.xsession-errors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
Fix Committed
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1341685] Re: When unconstrained, udm sometimes downloads files to wrong location
On Nov 17, 2014, at 10:36 PM, Manuel de la Peña wrote:
Any updates on when we can land this? Can I propose it for vivid?
Are there any blocks on vivid landings?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-download-manager in
Ubuntu.
https://bugs.launchpad.net/bugs/1341685
Title:
When unconstrained, udm sometimes downloads files to wrong location
Status in Ubuntu Download Manager:
In Progress
Status in “ubuntu-download-manager” package in Ubuntu:
In Progress
Status in “ubuntu-download-manager” package in Ubuntu RTM:
In Progress
Bug description:
I'm working on making the s-i tests more robust and I've run into an
odd situation, where udm sometimes stores its downloaded files using
an incorrect path, and not the one that s-i (which is unconstrained)
requests. This only appears to happen when the full s-i test suite is
run. When run in isolation, the test succeeds.
Here's a log of the createDownloadGroup call I'm making:
createDownloadGroup:
[Record(url='https://localhost:8943/gpg/blacklist.tar.xz',
destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz',
checksum=''),
Record(url='https://localhost:8943/gpg/blacklist.tar.xz.asc',
destination='/tmp/tmpe7mo8qm9/ubuntu/cache/keyring.tar.xz.asc',
checksum='')]
url is the source url, destination is the local path to save the file
in. This call produces incorrect destination paths in the 'finished'
signal:
FINISHED: dbus.Array([dbus.String('/home/barry/.local/share/ubuntu-
download-manager//usr/lib/telepathy/mission-
control-5/Downloads/blacklist (20).tar.xz'),
dbus.String('/home/barry/.local/share/ubuntu-download-
manager//usr/lib/telepathy/mission-control-5/Downloads/blacklist
(20).tar.xz.asc')], signature=dbus.Signature('s'))
Notice the very strange directory udm chooses which is definitely not
the path requested, and in fact doesn't exist. This matches the
observed behavior that after a succesful group download completion
(i.e. no errors occur), I assert that the requested destination path
exists, and in the failing test it does not.
I suspect some state is not getting reset in udm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-download-manager/+bug/1341685/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script
On Nov 18, 2014, at 02:41 PM, Martin Pitt wrote:
Bash's input redirection simply is way more powerful. Granted, bash
takes a tad longer to start up, but any tee or other external program
which you call in addition will probably hurt performance just as much.
Purely selfishly, switching back to bash would probably solve my original
problem since all my (ancient) startup/login scripts are bash syntax. ;)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
Fix Committed
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in .profile
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user .profile and .xprofile scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399687] Re: Provide version_detail for latest revision on server
** Also affects: ubuntu-system-image Importance: Undecided Status: New ** No longer affects: system-image (Ubuntu) ** Changed in: ubuntu-system-image Milestone: None = 3.0 ** Changed in: ubuntu-system-image Assignee: (unassigned) = Barry Warsaw (barry) ** Changed in: ubuntu-system-image Importance: Undecided = High ** Changed in: ubuntu-system-image Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1399687 Title: Provide version_detail for latest revision on server Status in Ubuntu system image (server/client/updater): Triaged Bug description: Currently, the Information() D-Bus method provides the following something like: current_build_number=129 device_name=generic_amd64 target_build_number=131 version_detail=ubuntu=20141205.1,raw-device=20141205.1,version=129 channel_name=ubuntu-core/devel last_update_date=2014-12-05 05:26:42 last_check_date=2014-12-05 15:41:43 Ideally, it would also provide version_detail for the latest revision on the server, that is version_detail for target_build_number. Even more ideally, it would break version_detail into chunks. Something like: current_ubuntu_version=ubuntu=20141205.1 current_raw_device_version=20141205.1 ... and for the latest revision found on the server, something like: target_ubuntu_version=ubuntu=20141205.9 target_raw_device_version=20141205.2 For bonus points, this information would also be available via 'system-image-cli -i', maybe requiring an addition option like '-- full' to avoid breaking existing consumers of 'system-image-cli -i' output. Note that the command-line accessibility is potentially more important than the D-Bus interface due to the fact that system-image-cli -i provides the '-C' option to point it at an alternative installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1399687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1278985] Re: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users
On Dec 06, 2014, at 02:29 PM, Andrea Azzarone wrote: Is this still a problem? No. It's not entirely discoverable, but it is possible to fix. -- 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/1278985 Title: Regression: Alt invocation of search cannot be remapped, causing pain to Emacs users Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: A long while ago, we Emacs users requested that it be possible to remap HUD search invocation away from Alt (and especially left-Alt) since this is a very common key chord prefix for Emacs. At some point this was done. In my recent bug LP: #1278582 I mentioned that the binding disappeared in the System Settings-Keyboard-Shortcuts window, but that bug has both been resolved, and a workaround was described by seb128 and tedg in irc that I could use gnome-control-center.real. That does indeed show me the Key to show the HUD setting. However, we still have a pain-inducing regression here ;). That setting is Disabled on my system, and yet the Unity/HUD search dialog is still invoked when hitting either left-Alt or right-Alt. Something consumes the first press of the Alt key so that it does not get passed to any window. I've confirmed this with Emacs, Claws-Mail, and Terminal. For example, if I hit Alt-F with focus in Emacs, Emacs does not see this key binding. If however, I only release the 'F' key, holding down Left-Alt, and then tap 'F' again, Emacs will see the key the second time. Claws exhibits very similar behavior (e.g. I have expunge bound to Alt-K - Claws only sees the second tap of Alt-K). Even worse, if in the course of trying to tap e.g. Alt-F in Emacs I happen to quickly tap Alt (either left or right), then the search dialog comes up and all subsequent typing is diverted to search instead of to Emacs. This is highly disruptive as you might imagine ;) At one point, I had hud and the launcher invocation remapped to Super (and right-Super in fact) and this is much more conducive to Emacs users. On my Trusty box where I've delayed updating to the latest archive packages, hud/unity search is still invoked by Super and *not* by Alt. However, on my fully updated Trusty machine, I experience this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1278985/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
I also have the problem on an Asus tower computer running 14.04 all by itself (no dual boot, no windows). I have found that I can get the speakers to work (at reduced volume) by leaving the headphones plugged into the headphone jack on the computer. Removing the headphones from the jack also kills the sound to the external speakers. Note that my computer seems to have at least four audio out jacks on the back and sound is not produced using the standard green jack. -- 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/1320020 Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I can get perfect sound through headphones, and the kernel recognizes the internal speaker, but nothing is ever played through it. I have personally tested a pair of earbuds to make sure that sound could play through the headphone port, and that isn't a problem. The sound driver just refuses to recognize the existence of the speaker, even though the kernel does. I wouldn't be surprised if the last upstream update had something to do with it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio CurrentDesktop: GNOME Date: Thu May 15 18:07:52 2014 InstallationDate: Installed on 2014-01-29 (106 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago) dmi.bios.date: 03/23/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0M7CYJ dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 1470 dmi.product.version: A05123 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1320020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1063350] Re: curl corrupts floating point context
On Dec 18, 2014, at 03:13 PM, Rolf Leggewie wrote: Feel free to close as fixed, if you ask me. Thanks. ** Changed in: pycurl (Ubuntu) Status: Incomplete = Fix Released ** Changed in: pycurl (Ubuntu Trusty) Status: Incomplete = Fix Released ** Changed in: pycurl (Ubuntu Utopic) Status: Incomplete = Fix Released ** Changed in: pycurl (Ubuntu Precise) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pycurl in Ubuntu. https://bugs.launchpad.net/bugs/1063350 Title: curl corrupts floating point context Status in pycurl package in Ubuntu: Fix Released Status in pycurl source package in Precise: Fix Released Status in pycurl source package in Trusty: Fix Released Status in pycurl source package in Utopic: Fix Released Bug description: # add-apt-repository ppa:ubuntu-wine/ppa You are about to add the following PPA to your system: Welcome to the Wine Team PPA. Here you can get the latest available Wine betas for every supported version of Ubuntu. This PPA is managed by Scott Ritchie and Maarten Lankhorst. More info: https://launchpad.net/~ubuntu-wine/+archive/ppa Press [ENTER] to continue or ctrl-c to cancel adding it Exception in thread Thread-1: Traceback (most recent call last): File /usr/lib/python2.7/threading.py, line 551, in __bootstrap_inner self.run() File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 99, in run self.add_ppa_signing_key(self.ppa_path) File /usr/lib/python2.7/dist-packages/softwareproperties/ppa.py, line 132, in add_ppa_signing_key tmp_keyring_dir = tempfile.mkdtemp() File /usr/lib/python2.7/tempfile.py, line 322, in mkdtemp name = names.next() File /usr/lib/python2.7/tempfile.py, line 141, in next letters = [choose(c) for dummy in 123456] File /usr/lib/python2.7/random.py, line 274, in choice return seq[int(self.random() * len(seq))] # raises IndexError if seq is empty ValueError: cannot convert float NaN to integer I have tried a purge and install but it doesn't fix this. No idea how to work around this. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.7.3 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sun Oct 7 18:43:46 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to precise on 2012-10-03 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycurl/+bug/1063350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385882] Re: Unable to mount iPad with IOS 8
Also occurs with iPhone 6 running iOS 8.1.2 (not just iPad). After plugging in my phone, I get two icons in the sidebar: My name's iPhone and iPhone. They look identical and offer the same right-click menu choices (Open, Name, Unlock from launcher). Only the first one works, though: when clicked, the file browser opens and displays the contents of the phone, and the sidebar menu gains a new right-click option Unmount. The second icon (iPhone) seems completely inert. So the error doesn't seem to prevent the phone from being mounted, but something's not quite right. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1385882 Title: Unable to mount iPad with IOS 8 Status in libimobiledevice package in Ubuntu: Confirmed Bug description: I can't mount my iPad after I upgraded to IOS 8. After plugging in I get a series of error messages, also my iPad keep asking wether I trust my computer. I get messages like: Unable to mount ...'s iPad: Location is already mounted - (it's not) Unable to mount iPhone: Unhandled lockdown error (-3) (also sometimes -20) If I remember correctly this happened last year after I upgraded to iOS 7. The problem exists in Utopic too. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libimobiledevice4 1.1.5+git20140313.bafe6a9e-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 26 14:36:14 2014 InstallationDate: Installed on 2014-01-10 (288 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: libimobiledevice UpgradeStatus: Upgraded to trusty on 2014-04-10 (198 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1385882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
By process of elimination (i.e. bisecting apt-get installs of all the dist-upgrade upgrading packages), I've narrowed this down to the following binary packages: libglib2.0-0 libglib2.0-bin libglib2.0-dev all part of the glib2.0 source package, version 2.41.2-1. In all likelihood it's the libglib2.0-0 (but harder to tell since all three must be upgraded at the same time). I've also confirmed that no change rebuilds of mono and gnome-do do *not* fix the problem. Something deeper has changed in the latest glib2.0 package to break gnome-do at least, and perhaps the entire mono runtime. Next I'll try to compare against Debian versions to see if anything out of sync needs updating. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- 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/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() Status in “glib2.0” package in Ubuntu: New Status in “gnome-do” package in Ubuntu: Confirmed Bug description: Do.exe crashed with SIGABRT in __GI_raise() ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: gnome-do 0.9-1build1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 18 17:47:01 2014 ExecutablePath: /usr/lib/gnome-do/Do.exe InstallationDate: Installed on 2014-05-16 (63 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) InterpreterPath: /usr/bin/mono-sgen ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe Signal: 6 SourcePackage: gnome-do StacktraceTop: __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 __GI_abort () at abort.c:89 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () Title: Do.exe crashed with SIGABRT in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1344386] Re: Do.exe crashed with SIGABRT in __GI_raise()
This seems to be the best I can manage for a traceback. Note that I had to manually hack /usr/lib/debug/usr/bin/mono-sgen-gdb.py to be Python 3 compatible (will file a separate bug on that). There are still some undefined symbols, but I can't suss out which packages are missing, and apport does not seem to want to cooperate to help me. Please let me know if there's more I information you want me to extract. OTOH, it's completely reproducible on utopic. Install gnome-do and then invoke that from the command line. ** Attachment added: typescript https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+attachment/4181007/+files/typescript -- 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/1344386 Title: Do.exe crashed with SIGABRT in __GI_raise() Status in “glib2.0” package in Ubuntu: New Status in “gnome-do” package in Ubuntu: Confirmed Bug description: Do.exe crashed with SIGABRT in __GI_raise() ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: gnome-do 0.9-1build1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jul 18 17:47:01 2014 ExecutablePath: /usr/lib/gnome-do/Do.exe InstallationDate: Installed on 2014-05-16 (63 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) InterpreterPath: /usr/bin/mono-sgen ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe Signal: 6 SourcePackage: gnome-do StacktraceTop: __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 __GI_abort () at abort.c:89 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () Title: Do.exe crashed with SIGABRT in __GI_raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1344386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
So, what changed recently? Did we get a new version of system-settings or (less likely to be affecting) ubuntu-download-manager? ** Also affects: ubuntu-system-image Importance: Undecided Status: New ** Tags added: client -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): New Status in “system-image” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365646] Re: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download
Does the monkey need a banana? ;) I tried a few scenarios with my n10 and cannot reproduce it so far. ** Changed in: ubuntu-system-image Status: New = Incomplete ** Changed in: system-image (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1365646 Title: Top Crasher: /usr/sbin/system-image-dbus:RuntimeError:_download Status in Ubuntu system image (server/client/updater): Incomplete Status in “system-image” package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding system-image. This problem was most recently seen with version 2.3.2-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/2ddecb9c81d025a9d1342a892298e1f9788500b6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1365646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1321481] Re: run integration tests from autopkgtest
** Changed in: ubuntu-system-image Milestone: None = 2.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1321481 Title: run integration tests from autopkgtest Status in Ubuntu system image (server/client/updater): Triaged Status in “system-image” package in Ubuntu: Triaged Bug description: system-image is a critical piece of infrastructure that needs to be kept in working order; changes should not be allowed to land in the archive that break it, since that risks leaving users high and dry on a phone image that's not upgradable. The best way to guard against this is by having system-image run a full battery of integration tests (including real system-image updates using ubuntu-emulator) from autopkgtest. This will prevent any direct dependencies of system-image from regressing system-image's functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1321481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396232] [NEW] Xorg freeze
Public bug reported: gnome-do and Xorg/unity/desktop seem to be incompatible on a fresh install of either utopic or vivid. This is either tied to 1080p (1920x1080) or a fresh install of either version. Details as I know them are provided here. I have a brand new machine which is running 1080p to an HDMI monitor. I installed Ubuntu 15.04 fresh from a usb install (usb-creator run from an existing, working vivid machine). As with all new machines, I go through my new install check list: https://wiki.ubuntu.com/BarryWarsaw These are slightly out of order, and this problem crops up after doing all the apt-get installs, apt-get update, and apt-get dist-upgrade. After all that, a reboot, and a re-login, the desktop is corrupt and unusable. I see the top menu bar extend from the right but only about 1/8th of the way to the left (the rest is desktop background), the dash only displayes on the lower left about 1/3 of the way up (again, desktop background the rest of the way), and neither the mouse nor the keyboard work at all. I must ssh in to reboot (or hard reboot of course). The system is still operational as the ssh shell works perfectly. The desktop is simply corrupt visually and unresponsive. The login screen after boot seems completely functional though. Mouse works fine as does the keyboard (or I wouldn't be able to log in!). Some additional data points make this even more interesting. On a different disk on this very same machine, I installed OS X 10.10.1, and VMware Fusion 7.0.1. Inside Fusion, I installed Vivid from daily live build iso of yesterday (11/24/14), and went through the same steps. I get exactly the same corruption and desktop freeze. I took a snapshot of the disk and then installed Utopic fresh from an iso downloaded via the normal www.ubuntu.com download site. In Utopic, I took a disk snapshot, and then I again went through the same apt-get steps and the desktop is again corrupt and frozen. This leads me to believe that one of the packages in my new machine buildout are to blame. I should also mention that in Vivid, I installed vmware-tools but in Utopic I did not. No difference (except that with vmware-tools I can set the display to 1920x1080, i.e. the full physical screen, while without vmware-tools, I cannot get full screen resolution from System Settings - Displays). Oh, I tried booting each of the previous kernels, with no effect. So now, I went back to the Utopic snapshot I took right after installing from iso and confirmed that everything works perfectly fine. Desktop is not corrupt and keyboard/mouse are responsive. Through the process of elimination, I would take a disk snapshot, install a few packages, test login, rinse and repeat. I was able to narrow it down to gnome-do and its dependencies. Specifically, after installing gnome-do and its dependencies, the desktop was broken as described above. Reverting to the disk snapshot pre-install of gnome-do, confirms that everything works fine. So now, I installed gnome-do and its dependencies, witnessed the corruption and freeze, and then ssh'd in and then did `apt-get purge gnome-do apt- get autoremove`. gnome-do and its dependencies were removed, I rebooted, logged in and everything was fine again. I went back to the Vivid disk snapshot, purged gnome-do and autoremoved, and *its* desktop was fixed. Clearly the problem is related to gnome-do in both Utopic and Vivid and/or one of its dependencies. After submitting this bug I will reboot back into Vivid running natively on the hardware, ssh in, purge gnome-do and its dependencies and see what happens. I suspect the desktop will be fixed again. As if this is not interesting enough, I have two other desktops currently running Vivid, and both have gnome-do installed, *and* both work perfectly well! The big difference here is that both of them have been dist-upgraded to Vivid through existing Utopic releases, and before that, even Trusty. IOW, both machines were running at least Trusty, upgraded to Utopic, upgraded to Vivid, and work perfectly fine. No desktop corruption, no freezes. (One machine has been upgraded successively since at least Precise; both machines are now on the 'devel' channel.) I'm happy to continue helping with this in any way necessary. Let me know if you need any other information or have anything you want me to test. I will let you bugtask this to unity and/or gnome-do or some other dependency, as you see fit. Thanks! ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu10 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: Tue Nov 25 10:59:11 2014
[Touch-packages] [Bug 1396232] Re: Xorg freeze
** Also affects: gnome-do (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1396232 Title: Xorg freeze Status in “gnome-do” package in Ubuntu: New Status in “xorg” package in Ubuntu: New Bug description: gnome-do and Xorg/unity/desktop seem to be incompatible on a fresh install of either utopic or vivid. This is either tied to 1080p (1920x1080) or a fresh install of either version. Details as I know them are provided here. I have a brand new machine which is running 1080p to an HDMI monitor. I installed Ubuntu 15.04 fresh from a usb install (usb-creator run from an existing, working vivid machine). As with all new machines, I go through my new install check list: https://wiki.ubuntu.com/BarryWarsaw These are slightly out of order, and this problem crops up after doing all the apt-get installs, apt-get update, and apt-get dist-upgrade. After all that, a reboot, and a re-login, the desktop is corrupt and unusable. I see the top menu bar extend from the right but only about 1/8th of the way to the left (the rest is desktop background), the dash only displayes on the lower left about 1/3 of the way up (again, desktop background the rest of the way), and neither the mouse nor the keyboard work at all. I must ssh in to reboot (or hard reboot of course). The system is still operational as the ssh shell works perfectly. The desktop is simply corrupt visually and unresponsive. The login screen after boot seems completely functional though. Mouse works fine as does the keyboard (or I wouldn't be able to log in!). Some additional data points make this even more interesting. On a different disk on this very same machine, I installed OS X 10.10.1, and VMware Fusion 7.0.1. Inside Fusion, I installed Vivid from daily live build iso of yesterday (11/24/14), and went through the same steps. I get exactly the same corruption and desktop freeze. I took a snapshot of the disk and then installed Utopic fresh from an iso downloaded via the normal www.ubuntu.com download site. In Utopic, I took a disk snapshot, and then I again went through the same apt-get steps and the desktop is again corrupt and frozen. This leads me to believe that one of the packages in my new machine buildout are to blame. I should also mention that in Vivid, I installed vmware-tools but in Utopic I did not. No difference (except that with vmware-tools I can set the display to 1920x1080, i.e. the full physical screen, while without vmware-tools, I cannot get full screen resolution from System Settings - Displays). Oh, I tried booting each of the previous kernels, with no effect. So now, I went back to the Utopic snapshot I took right after installing from iso and confirmed that everything works perfectly fine. Desktop is not corrupt and keyboard/mouse are responsive. Through the process of elimination, I would take a disk snapshot, install a few packages, test login, rinse and repeat. I was able to narrow it down to gnome-do and its dependencies. Specifically, after installing gnome-do and its dependencies, the desktop was broken as described above. Reverting to the disk snapshot pre-install of gnome-do, confirms that everything works fine. So now, I installed gnome-do and its dependencies, witnessed the corruption and freeze, and then ssh'd in and then did `apt-get purge gnome-do apt-get autoremove`. gnome-do and its dependencies were removed, I rebooted, logged in and everything was fine again. I went back to the Vivid disk snapshot, purged gnome-do and autoremoved, and *its* desktop was fixed. Clearly the problem is related to gnome-do in both Utopic and Vivid and/or one of its dependencies. After submitting this bug I will reboot back into Vivid running natively on the hardware, ssh in, purge gnome-do and its dependencies and see what happens. I suspect the desktop will be fixed again. As if this is not interesting enough, I have two other desktops currently running Vivid, and both have gnome-do installed, *and* both work perfectly well! The big difference here is that both of them have been dist-upgraded to Vivid through existing Utopic releases, and before that, even Trusty. IOW, both machines were running at least Trusty, upgraded to Utopic, upgraded to Vivid, and work perfectly fine. No desktop corruption, no freezes. (One machine has been upgraded successively since at least Precise; both machines are now on the 'devel' channel.) I'm happy to continue helping with this in any way necessary. Let me know if you need any other information or have anything you want me to test. I will let you bugtask this to unity and/or gnome-do or some other dependency, as you see fit. Thanks!
[Touch-packages] [Bug 1399687] Re: Provide version_detail for latest revision on server
** Tags added: client -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1399687 Title: Provide version_detail for latest revision on server Status in system-image package in Ubuntu: New Bug description: Currently, the Information() D-Bus method provides the following something like: current_build_number=129 device_name=generic_amd64 target_build_number=131 version_detail=ubuntu=20141205.1,raw-device=20141205.1,version=129 channel_name=ubuntu-core/devel last_update_date=2014-12-05 05:26:42 last_check_date=2014-12-05 15:41:43 Ideally, it would also provide version_detail for the latest revision on the server, that is version_detail for target_build_number. Even more ideally, it would break version_detail into chunks. Something like: current_ubuntu_version=ubuntu=20141205.1 current_raw_device_version=20141205.1 ... and for the latest revision found on the server, something like: target_ubuntu_version=ubuntu=20141205.9 target_raw_device_version=20141205.2 For bonus points, this information would also be available via 'system-image-cli -i', maybe requiring an addition option like '-- full' to avoid breaking existing consumers of 'system-image-cli -i' output. Note that the command-line accessibility is potentially more important than the D-Bus interface due to the fact that system-image-cli -i provides the '-C' option to point it at an alternative installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1399687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371703] Re: No fallback if the system update process fails at any point
** No longer affects: system-image (Ubuntu) ** Changed in: ubuntu-system-image Status: New = Triaged ** Changed in: ubuntu-system-image Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1371703 Title: No fallback if the system update process fails at any point Status in Ubuntu system image (server/client/updater): Triaged Bug description: For someone to install a system update, all of the following need to be true: (A) The phone needs to start up completely. (B) Unity needs to not crash. (C) The networking stack needs to let Ubuntu check for updates. (D) If System Settings is not in the Launcher, the Apps scope needs to not crash. (E) System Settings needs to launch without crashing. (F) The System Settings Updates screen needs to open without crashing. (G) The system-image update system itself needs to work properly. This is a long and brittle chain. If *any one* of these steps breaks, the phone is no longer updateable. And at worst -- if A, B, or C fails -- the phone is effectively bricked. This is not a theoretical problem. On Ubuntu for PC, crasher bugs in update-manager often persist for a long time in the list of most common errors, because the updates that fix them can't themselves be installed until a nearby geek cracks out a terminal to use apt-get. That's not so practical on a phone. Therefore, there should be a fallback path for installing system image updates in emergency situations. This path may not avoid all of the requirements listed above, but it should avoid as many as practical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1371703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416328] Re: Does not reply on dbus when busy (e.g. downloading)
** Also affects: ubuntu-system-image Importance: Undecided Status: New ** Tags added: client ** No longer affects: system-image (Ubuntu) ** Changed in: ubuntu-system-image Status: New = Triaged ** Changed in: ubuntu-system-image Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1416328 Title: Does not reply on dbus when busy (e.g. downloading) Status in Ubuntu system image (server/client/updater): Triaged Bug description: We ran into the issue that system-image-dbus would sometimes not reply on snappy. After long debugging and deep dive into the go-dbus code it seems that system-image-dbus simply does not reply when its busy, at least in the snappy branch. This may well be fixed in the 3.0 branch so here is a test and it would be great to know if that works with the curl backend and the 3.0 branch: Ensure there is something for s-i-dbus to do (e.g. download new image): $ rm -f /writable/cache/*.tar.xz $ dbus-send --system --dest=com.canonical.SystemImage --type=method_call --print-reply /Service com.canonical.SystemImage.CheckForUpdate sleep 1 dbus-send --system --dest=com.canonical.SystemImage --type=method_call --print- reply /Service com.canonical.SystemImage.DownloadUpdate sleep 1 dbus-send --system --dest=com.canonical.SystemImage --type=method_call --reply-timeout=5000 --print-reply /Service com.canonical.SystemImage.Information Running the above gives me: method return sender=:1.54 - dest=:1.53 reply_serial=2 method return sender=:1.54 - dest=:1.55 reply_serial=2 Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. So it appears the curl backend is not quite there for snappy yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-image/+bug/1416328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
