[Touch-packages] [Bug 1452099] Re: unshare -r is broken
** Changed in: util-linux (Debian) Status: Unknown = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1452099 Title: unshare -r is broken Status in util-linux package in Ubuntu: New Status in util-linux package in Debian: Fix Released Bug description: After CVE-2014-8989 was fixed in Linux v3.19-rc1~41, ‘unshare -r’ no longer works. $ unshare -Ur unshare: write failed /proc/self/gid_map: Operation not permitted $ sudo -i # unshare -r unshare: write failed /proc/self/gid_map: Operation not permitted This was fixed in Debian’s util-linux 2.25.2-6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1452099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417826] Re: display acting up. overlay .. ?
Morten Hundevad, to clarify, is this reproducible with GNOME Flashback (metacity)? -- 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/1417826 Title: display acting up. overlay .. ? Status in xorg package in Ubuntu: Expired Bug description: With nvidia 331.113 or 346.59 after configuring dual screen layout via System Tools Settings Displays, sometimes both screens are on the same monitor and it scrolls sideways. However, if I remove this manually configured layout it fails (in what way?). With nvidia 304 my second monitor stopped working. WORKAROUND: Use nouveau. However, nvidia out performs it. WORKAROUND: Use GNOME Flashback (Metacity). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Er et filkatalog: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.1 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: Wed Feb 4 01:29:47 2015 DistUpgraded: 2014-11-11 23:22:24,600 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0571] NVIDIA Corporation GF116M [GeForce GT 555M/635M] [10de:124d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GT 555M [1028:0571] InstallationDate: Installed on 2014-10-11 (115 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Dell System XPS L702X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=81abd60b-9317-4293-accd-cf625ddbaa45 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to utopic on 2014-11-11 (84 days ago) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0XN71K dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA19:bd09/07/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L702X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Feb 3 20:36:12 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5920 vendor CMO xserver.version: 2:1.16.0-1ubuntu1.2 --- .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.76 Thu Jan 22 12:11:08 PST 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistUpgraded: 2015-04-24 05:17:39,607 DEBUG enabling apt cron job DistroCodename: vivid DistroRelease: Ubuntu 15.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-34-generic, x86_64: installed bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed nvidia-340, 340.76, 3.16.0-34-generic, x86_64: installed nvidia-340, 340.76, 3.19.0-15-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA
[Touch-packages] [Bug 1447931] Re: alt-tab switches windows from multiple monitors
** Tags added: ui ** Tags added: alt-tab compiz -- 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/1447931 Title: alt-tab switches windows from multiple monitors Status in unity package in Ubuntu: New Bug description: When using multiple monitors, alt-tab shows and switches between not only windows from current monitor, but from both. That makes navigating between windows much harder, especially when it comes to switching between 4 instances of application of one type, spread on multiple monitors (for example having 2 terminals per monitor). Bug is present in Ubuntu 14.04 LTS in Unity 7.2.4. How to reproduce? Plug in another monitor and launch many windows on both screens. Try to alt-tab efficiently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1447931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452098] Re: [Launcher]home button can not setcurrentscope as you want
my first scope is clickscope.in shell.qml we can see the function of showHome, when you click dashhome button(on launcher), it will be called,and there is a line: dash.setCurrentScope(0, animate, true), it means that if we click dashhome button, dash will be shown and must show us the clickscope 1.swipe to clickscope 2.click home button (dash will show us clickscope, that's right) 3.swipe to video scope 4. click home button 5.dash will show us video scope but not clickscope (dash must show us clickscope as code written ) 6.qtcreator run unity8 and unity8-dash 7. do step 1 to 8, it will be shown as code says -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1452098 Title: [Launcher]home button can not setcurrentscope as you want Status in unity8 package in Ubuntu: Incomplete Bug description: every time you click home button it will show you clickscope, when you swipe to another scope,for example video, you click home button, you should be shown clickscope as code want (in shell.qml, there is a function showHome() and a line code dash.setCurrentScope(),you can change arguments you want), but only focused unity8-dash, in an interesting condition ,when you runs unity8 and unity8-dash with qtcreator, everything works fine, maybe it means the function of setCurrentScope() has some trouble; what i can see in unity8.log may be about to this condition is below: UbuntuClipboard - Failed to get system clipboard contents via D-Bus. org.freedesktop.DBug.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 xepired, or the network connections was broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1452098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437182] Re: maliit-framework fails to build against Qt 5.5
Wily is now open. This would be nice to get landed there at some point before Qt 5.5 gets released. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1437182 Title: maliit-framework fails to build against Qt 5.5 Status in maliit-framework package in Ubuntu: New Bug description: Build log:https://launchpadlibrarian.net/201366368/buildlog_ubuntu- vivid-amd64.maliit- framework_0.99.0%2Bgit20130923%2B17fdf86-0ubuntu9~vivid1~test1~qt550alpha1_BUILDING.txt.gz --- main.cpp:67:12: error: enumeration value 'QtInfoMsg' not handled in switch [-Werror=switch] switch (type) { ^ --- This build was against 5.5.0 alpha, but being feature complete it's likely the bug will persist. A fix would be very welcome in the way that compiling against both Qt 5.4 and Qt 5.5 would work via for example #ifdef. That way a no-change rebuild would make landing process simpler. More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1437182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447807] Re: systemctl enable fails to enable a SysV service
Thanks for the fast fix, is there already a package built from the patch somewhere that I could test? Also you might want to amend the title of the bug, as enabling the service is in fact performed properly, systemctl just throws an error in the end when it should simply terminate successfully instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447807 Title: systemctl enable fails to enable a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: In Progress Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen
It appens to me also, after every 2-3 locks... ** Attachment added: _usr_bin_compiz.1000.crash https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+attachment/4392068/+files/_usr_bin_compiz.1000.crash -- 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/1451613 Title: Unity/compiz crashes when locking screen Status in unity package in Ubuntu: New Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452211] Re: Wizard crashes when viewing HERE terms and conditions
Is this a dupe of https://bugs.launchpad.net/ubuntu/+source/oxide- qt/+bug/1439829 ? ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1452211 Title: Wizard crashes when viewing HERE terms and conditions Status in unity8 package in Ubuntu: Incomplete Bug description: Test case. 1. During the wizard, switch to Spanish. 2. Fill wifi credentials. 3. In Term Conditions, tap to read the HERE terms. 4. In this screen tap in the URL of the HERE terms. 5. Go back to main Term Conditions. 6. Repeat steps 3 to 5. Expected result. - No crash. Actual result. - Unity crashes and reboots. current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1452211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452216] [NEW] libgcrypt11 not present in Vivid (15.04) - Spotify and other app issue.
Public bug reported: The package libgcrypt11 is not present anymore in official ubuntu vivid repositories. This cause app crash, such as spotify: spotify: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory Current workaround is to manually download the .deb package from launchpad/debian package such as https://packages.debian.org/wheezy/libgcrypt11 and manually install with dpkg. Linux SAGITTER 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 15.04 Release:15.04 Codename: vivid ** Affects: libgcrypt11 (Ubuntu) Importance: Undecided Status: New ** Tags: libgcrypt11 spotify ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgcrypt11 in Ubuntu. https://bugs.launchpad.net/bugs/1452216 Title: libgcrypt11 not present in Vivid (15.04) - Spotify and other app issue. Status in libgcrypt11 package in Ubuntu: New Bug description: The package libgcrypt11 is not present anymore in official ubuntu vivid repositories. This cause app crash, such as spotify: spotify: error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory Current workaround is to manually download the .deb package from launchpad/debian package such as https://packages.debian.org/wheezy/libgcrypt11 and manually install with dpkg. Linux SAGITTER 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/1452216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452219] [NEW] Wishlist: ring-ring ringtone
Public bug reported: The supplied ringtones are pretty, but not suitable for use in a professional environment. It is not possible to add ringtones without remounting rw, so a ring-ring type ringtone should be supplied by default. I have supplied a bland/loud office-style ringtone which may serve the purpose. This is an original work created by the tone generators and filters in Audacity and has not been copied or derived from another source. If you wish to use it, I am happy to change the licence from the Creative Commons Attribution-ShareAlike 4.0 International License, if required. ** Affects: ubuntu-touch-sounds (Ubuntu) Importance: Undecided Status: New ** Attachment added: Office ringtone. This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License but I would be happy to change this if required. https://bugs.launchpad.net/bugs/1452219/+attachment/4392100/+files/office.ogg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-sounds in Ubuntu. https://bugs.launchpad.net/bugs/1452219 Title: Wishlist: ring-ring ringtone Status in ubuntu-touch-sounds package in Ubuntu: New Bug description: The supplied ringtones are pretty, but not suitable for use in a professional environment. It is not possible to add ringtones without remounting rw, so a ring-ring type ringtone should be supplied by default. I have supplied a bland/loud office-style ringtone which may serve the purpose. This is an original work created by the tone generators and filters in Audacity and has not been copied or derived from another source. If you wish to use it, I am happy to change the licence from the Creative Commons Attribution-ShareAlike 4.0 International License, if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-sounds/+bug/1452219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452161] Re: from flight mode to normal mode with 2 SIM: PIN's title prompt is reversed
I am not sure if the indicator for unity7 and before is the same project for unity8 indicator, so please re-adjust target if needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1452161 Title: from flight mode to normal mode with 2 SIM: PIN's title prompt is reversed Status in indicator-network package in Ubuntu: New Bug description: I am on krillin #21 on rtm/stable channel. * I go on flight mode (the checkbox from the indicator becomes green) * I go out flight mode (the checkbox from the indicator is not anymore green) * I have 2 button to unlock the SIM 1 and SIM 2 * I click on unlock SIM 1, I have a screen with the title unlock SIM 2 * I click on unlock SIM 2, I have s screen with the title unlock SIM 1 Since I have the same PIN, I am not sure if the button call to unlock the wrong SIM, on if it's only the wrong title. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1452161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382567] Re: Top Crasher: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': free(): invalid pointer: ADD
Reopening. The linked bug claims to be fixed but this is still happening on both 14.09 and vivid, and is the second most common such crasher: https://errors.ubuntu.com/problem/69d0dabacb1ee1cc5be6fba75784a0751c80617d (login if not logged in) ** Changed in: unity-scopes-api (Ubuntu) Status: Invalid = Won't Fix ** Changed in: unity-scopes-api (Ubuntu) Status: Won't Fix = Confirmed ** Changed in: savilerow Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1382567 Title: Top Crasher: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': free(): invalid pointer: ADDR *** Status in The Savilerow project: Confirmed Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-scopes-api. This problem was most recently seen with version 0.6.7+14.10.20141010.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/69d0dabacb1ee1cc5be6fba75784a0751c80617d contains more details. Steps to reproduce: 1. Swipe up from bottom of screen and select dashboard 2. Swipe up from bottom of screen and select apps expected result: no crash actual result: crash To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1382567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444402] Re: While sbuilding in LXC, systemd loops attempting to umount the underlay
In my local container, http://cgit.freedesktop.org/systemd/systemd/commit/?id=f62009410 (which was the fix in the above PPA) helps already. However, it doesn't in the cloud instance: The main difference there is that in that cloud instance udev is running while in my local container it isn't (it's not usually meant to run in LXC). Adding these options in the container starts udev and reproduces this issue again: lxc.mount.auto = sys:rw cgroup lxc.mount.entry = /etc/schroot /srv/lxc/test/rootfs/etc/schroot none bind 0 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/102 Title: While sbuilding in LXC, systemd loops attempting to umount the underlay Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Vivid: In Progress Bug description: I recently hit ENOSPC which turned out to be the result of various syslogs from the current and previous boots totalling up to 30G. They were filled with messages like Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid umount[31795]: umount: /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734: target is busy Apr 15 11:22:35 vivid umount[31795]: (In some cases useful info about processes that Apr 15 11:22:35 vivid umount[31795]: use the device is found by lsof(8) or fuser(1).) Apr 15 11:22:35 vivid systemd[1]: var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount mount process exited, code=exited status=32 Apr 15 11:22:35 vivid systemd[1]: Failed unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid systemd[1]: Unmounted /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount entered failed state. looping constantly for the duration of any builds in sbuild. Why is systemd trying to do this? laney@vivid apt-cache policy systemd systemd: Installed: 219-7ubuntu1 Candidate: 219-7ubuntu1 Version table: *** 219-7ubuntu1 0 500 http://sherwood/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452172] [NEW] /usr/bin/ubuntu-location-serviced:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:std:::start_thread
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding location-service. This problem was most recently seen with version 2.1+15.04.20150226-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a5c9479b0e3f4ccc0329d8f9316d8cae6da2639e contains more details. ** Affects: location-service (Ubuntu) Importance: Undecided Status: New ** Tags: rtm-14.09 utopic vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1452172 Title: /usr/bin/ubuntu-location- serviced:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:std:::start_thread Status in location-service package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding location-service. This problem was most recently seen with version 2.1+15.04.20150226-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/a5c9479b0e3f4ccc0329d8f9316d8cae6da2639e contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1452172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295909] Re: Unity spread trigger ruins windows and freezes desktop
When you get this crash, please upload the /var/crash/_usr_bin_compiz.*.crash file that gets generated, or we don't have enough info to debug this. Thanks. -- 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/1295909 Title: Unity spread trigger ruins windows and freezes desktop Status in Compiz: Triaged Status in Unity: Confirmed Status in compiz package in Ubuntu: Triaged Status in unity package in Ubuntu: Confirmed Bug description: The latest update disabled window spreading and when triggered crashes the desktop. Everything freezes and windows cannot be switched. The only way to close an application is to shut down. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 21 20:59:17 2014 DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (77 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: TOSHIBA Satellite C55-A ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-18-generic root=UUID=6b37c83b-b64c-42fc-89d3-3db46a397734 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-20 (1 days ago) dmi.bios.date: 04/12/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.10 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.10:bd04/12/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCF6U-01Y00C:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C55-A dmi.product.version: PSCF6U-01Y00C dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 10.0.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 21 18:56:33 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17223 vendor SDC xserver.version: 2:1.15.0-1ubuntu7 --- .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-19-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (83 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: TOSHIBA Satellite C55-A Package: unity PackageArchitecture: all ProcKernelCmdLine:
[Touch-packages] [Bug 1432613] Re: Facebook and MSN messengers shutting down (third-party client access)
Hi Brian, I tested the packages in vivid-proposed and they did work fine. I'd like to test them in trusty-proposed too, but they have not been uploaded there, have they? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1432613 Title: Facebook and MSN messengers shutting down (third-party client access) Status in Online Accounts: Account plugins: In Progress Status in Webapps Team Task Tracking Project: In Progress Status in account-plugins package in Ubuntu: Fix Committed Status in empathy package in Ubuntu: Fix Committed Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in account-plugins source package in Trusty: Fix Committed Status in empathy source package in Trusty: In Progress Status in ubuntu-system-settings-online-accounts source package in Trusty: Won't Fix Status in account-plugins source package in Utopic: Fix Committed Status in empathy source package in Utopic: Fix Committed Status in ubuntu-system-settings-online-accounts source package in Utopic: Won't Fix Status in account-plugins source package in Vivid: Fix Committed Status in empathy source package in Vivid: Fix Committed Status in ubuntu-system-settings-online-accounts source package in Vivid: Won't Fix Bug description: [ Description ] Facebook messenger and Windows Live messenger don't work any more because Facebook Microsoft removed third-party support for them. [ Fix QA ] Stop supporting IM accounts for these clients. For both creation continued use. Verify that if you add a WLM or FB account in online accounts, empathy doesn't try to connect to it. account-plugins-windows-live shouldn't be pulled in by default any more (check a trusty daily which is built with proposed). [ Regression potential ] This is a regression, in that we stop supporting some account types. We don't have a choice about this. [ Original description ] The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. I guess we need to correspondingly remove IM support for these services SRU it back. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1432613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452161] [NEW] from flight mode to normal mode with 2 SIM: PIN's title prompt is reversed
Public bug reported: I am on krillin #21 on rtm/stable channel. * I go on flight mode (the checkbox from the indicator becomes green) * I go out flight mode (the checkbox from the indicator is not anymore green) * I have 2 button to unlock the SIM 1 and SIM 2 * I click on unlock SIM 1, I have a screen with the title unlock SIM 2 * I click on unlock SIM 2, I have s screen with the title unlock SIM 1 Since I have the same PIN, I am not sure if the button call to unlock the wrong SIM, on if it's only the wrong title. ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Tags: krillin next unity8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1452161 Title: from flight mode to normal mode with 2 SIM: PIN's title prompt is reversed Status in indicator-network package in Ubuntu: New Bug description: I am on krillin #21 on rtm/stable channel. * I go on flight mode (the checkbox from the indicator becomes green) * I go out flight mode (the checkbox from the indicator is not anymore green) * I have 2 button to unlock the SIM 1 and SIM 2 * I click on unlock SIM 1, I have a screen with the title unlock SIM 2 * I click on unlock SIM 2, I have s screen with the title unlock SIM 1 Since I have the same PIN, I am not sure if the button call to unlock the wrong SIM, on if it's only the wrong title. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1452161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452171] [NEW] No password field appears after wake from sleep
Public bug reported: To reproduce, close laptop lid and allow to go to sleep. Some time later, open laptop lid. No password field appears and I can't unlock the screen, see attached screenshot. This only happens sometimes (maybe one in ten or fewer?). It seems very similar to another bug which is allegedly fixed, so I have raised this one. The mouse cursor moves. Ctrl-Alt-F1 to a terminal and sudo services restart lightdm restarts X but still results in no password field. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 6 09:32:46 2015 InstallationDate: Installed on 2015-04-05 (30 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-04-23 (12 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: Selection of logs which I scraped from the machine before I restarted it. https://bugs.launchpad.net/bugs/1452171/+attachment/4392005/+files/logs.tar.gz -- 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/1452171 Title: No password field appears after wake from sleep Status in unity package in Ubuntu: New Bug description: To reproduce, close laptop lid and allow to go to sleep. Some time later, open laptop lid. No password field appears and I can't unlock the screen, see attached screenshot. This only happens sometimes (maybe one in ten or fewer?). It seems very similar to another bug which is allegedly fixed, so I have raised this one. The mouse cursor moves. Ctrl-Alt-F1 to a terminal and sudo services restart lightdm restarts X but still results in no password field. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 6 09:32:46 2015 InstallationDate: Installed on 2015-04-05 (30 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-04-23 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1452171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452173] [NEW] [Dell Precision M4800] Regression: screen brightness control broken in 15.04
Public bug reported: In Ubuntu 15.04, I no longer am able to control the screen brightness. See possible similar bug #1411514 for 14.04.1. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Date: Wed May 6 10:12:03 2015 DistUpgraded: 2015-04-24 01:12:19,566 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] InstallationDate: Installed on 2014-03-12 (419 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Precision M4800 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=61c860cd-d55d-4e70-85a3-615b677b5811 ro nomodeset=1 splash quiet plymouth:debug=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-04-23 (12 days ago) dmi.bios.date: 12/03/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 5 22:22:48 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-346-updates (Ubuntu) Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install regression-release ubuntu vivid ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-346-updates (Ubuntu) Importance: Undecided Status: New ** Tags added: regression-release -- 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/1452173 Title: [Dell Precision M4800] Regression: screen brightness control broken in 15.04 Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-346-updates package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: In Ubuntu 15.04, I no longer am able to control the screen brightness. See possible similar bug #1411514 for 14.04.1. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Date: Wed May 6 10:12:03 2015 DistUpgraded: 2015-04-24 01:12:19,566 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For
[Touch-packages] [Bug 1452171] Re: No password field appears after wake from sleep
Bug seems similar to https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311316 which is supposed to be fixed. -- 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/1452171 Title: No password field appears after wake from sleep Status in unity package in Ubuntu: New Bug description: To reproduce, close laptop lid and allow to go to sleep. Some time later, open laptop lid. No password field appears and I can't unlock the screen, see attached screenshot. This only happens sometimes (maybe one in ten or fewer?). It seems very similar to another bug which is allegedly fixed, so I have raised this one. The mouse cursor moves. Ctrl-Alt-F1 to a terminal and sudo services restart lightdm restarts X but still results in no password field. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 6 09:32:46 2015 InstallationDate: Installed on 2015-04-05 (30 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-04-23 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1452171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452177] [NEW] /usr/bin/mtp-server:6:google::DumpStackTraceAndExit:google::LogMessage::Fail:google::LogMessage::SendToLog:google::LogMessage::Flush:google::LogMessageFatal::~LogM
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding mtp. This problem was most recently seen with version 0.0.4+15.04.20150219-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11c89f74f8521a10d25e21812c53ec20578c4f94 contains more details. ** Affects: mtp (Ubuntu) Importance: Undecided Status: New ** Tags: kylin-15.04 rtm-14.09 utopic vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1452177 Title: /usr/bin/mtp- server:6:google::DumpStackTraceAndExit:google::LogMessage::Fail:google::LogMessage::SendToLog:google::LogMessage::Flush:google::LogMessageFatal::~LogMessageFatal Status in mtp package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mtp. This problem was most recently seen with version 0.0.4+15.04.20150219-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/11c89f74f8521a10d25e21812c53ec20578c4f94 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1452177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452171] Re: No password field appears after wake from sleep
** Attachment added: Photo of issue, how do I log in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1452171/+attachment/4392010/+files/20150506_091836.jpg -- 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/1452171 Title: No password field appears after wake from sleep Status in unity package in Ubuntu: New Bug description: To reproduce, close laptop lid and allow to go to sleep. Some time later, open laptop lid. No password field appears and I can't unlock the screen, see attached screenshot. This only happens sometimes (maybe one in ten or fewer?). It seems very similar to another bug which is allegedly fixed, so I have raised this one. The mouse cursor moves. Ctrl-Alt-F1 to a terminal and sudo services restart lightdm restarts X but still results in no password field. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 6 09:32:46 2015 InstallationDate: Installed on 2015-04-05 (30 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-04-23 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1452171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452179] [NEW] /usr/bin/mediascanner-service-2.0:11:gst_caps_features_is_equal:gst_caps_is_subset:gst_element_factory_list_filter:gst_uri_decode_bin_autoplug_factories:ffi_call_V
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding mediascanner2. This problem was most recently seen with version 0.105+15.04.20150204~rtm-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/943504c7cae2daa6040e3e1318f5f4b274af592c contains more details. ** Affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New ** Tags: rtm-14.09 vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1452179 Title: /usr/bin/mediascanner- service-2.0:11:gst_caps_features_is_equal:gst_caps_is_subset:gst_element_factory_list_filter:gst_uri_decode_bin_autoplug_factories:ffi_call_VFP Status in mediascanner2 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mediascanner2. This problem was most recently seen with version 0.105+15.04.20150204~rtm-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/943504c7cae2daa6040e3e1318f5f4b274af592c contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1452179/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452211] [NEW] Wizard crashes when viewing HERE terms and conditions
Public bug reported: Test case. 1. During the wizard, switch to Spanish. 2. Fill wifi credentials. 3. In Term Conditions, tap to read the HERE terms. 4. In this screen tap in the URL of the HERE terms. 5. Go back to main Term Conditions. 6. Repeat steps 3 to 5. Expected result. - No crash. Actual result. - Unity crashes and reboots. current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed ** Affects: unity8 (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: qa-regression ** Attachment added: _usr_bin_system-settings-wizard.32011.crash https://bugs.launchpad.net/bugs/1452211/+attachment/4392085/+files/_usr_bin_system-settings-wizard.32011.crash ** Package changed: oxide-qt (Ubuntu) = unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1452211 Title: Wizard crashes when viewing HERE terms and conditions Status in unity8 package in Ubuntu: Incomplete Bug description: Test case. 1. During the wizard, switch to Spanish. 2. Fill wifi credentials. 3. In Term Conditions, tap to read the HERE terms. 4. In this screen tap in the URL of the HERE terms. 5. Go back to main Term Conditions. 6. Repeat steps 3 to 5. Expected result. - No crash. Actual result. - Unity crashes and reboots. current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1452211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452173] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1452173 Title: [Dell Precision M4800] Regression: screen brightness control broken in 15.04 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346-updates package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: In Ubuntu 15.04, I no longer am able to control the screen brightness. See possible similar bug #1411514 for 14.04.1. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Date: Wed May 6 10:12:03 2015 DistUpgraded: 2015-04-24 01:12:19,566 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] InstallationDate: Installed on 2014-03-12 (419 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Precision M4800 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=61c860cd-d55d-4e70-85a3-615b677b5811 ro nomodeset=1 splash quiet plymouth:debug=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-04-23 (12 days ago) dmi.bios.date: 12/03/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 5 22:22:48 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1167314] Re: software-properties-gtk crashed with FileNotFoundError in _execute_child(): [Errno 2] Arquivo ou diretório não encontrado: '/usr/lib/indicator-session/gtk-logout-hel
I was just hit by this on XUbuntu 14.04 as well. The Apport submit dialog identified my problem as a duplicate of this bug, but I found https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1429185 which looks like a better place to continue discussions if you are on Xubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1167314 Title: software-properties-gtk crashed with FileNotFoundError in _execute_child(): [Errno 2] Arquivo ou diretório não encontrado: '/usr/lib/indicator-session/gtk-logout-helper' Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Saucy: Fix Released Bug description: Português desculpe-me, eu não sei bem o inglês, então usei o google tradutor para criar esse texto. O erro ocorreu depois que instalei o Driver Nvidia 313 (proprietário), após instalar e aperta o botão reiniciar, na mesma janela, o erro ocorreu. English I'm sorry, I do not know much English, so I used the google translator to create this text. The error occurred after I installed the Nvidia Driver 313 (owner), and after installing presses the reset button in the same window, the error occurred. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: software-properties-gtk 0.92.17 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Wed Apr 10 09:11:39 2013 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2013-04-10 (0 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Alpha amd64 (20130328) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_BR.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/software-properties-gtk'] SourcePackage: software-properties Title: software-properties-gtk crashed with FileNotFoundError in _execute_child(): [Errno 2] Arquivo ou diretório não encontrado: '/usr/lib/indicator-session/gtk-logout-helper' 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/software-properties/+bug/1167314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429185] Re: Restart button in Additional Drivers does not restart Xubuntu
I just got hit by this as well. The bug also triggered an Apport dialog, which (IMHO erroneously) pointed to https://bugs.launchpad.net/ubuntu/+source/software- properties/+bug/1167314. I guess the action linked from the software-properties-gtk Restart... button ought to be configurable by a packaged setting. For XFCE, it looks (by quick googling) like xfce4-session-logout --reboot would be a suitable value for XUbuntu. $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.92.37.3 Candidate: 0.92.37.3 Version table: *** 0.92.37.3 0 500 http://fi.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.92.36 0 $ grep -rF gnome-session-quit /usr/lib/python3/dist-packages/softwareproperties/gtk Binary file /usr/lib/python3/dist-packages/softwareproperties/gtk/__pycache__/SoftwarePropertiesGtk.cpython-34.pyc matches /usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py: subprocess.call(['gnome-session-quit', '--reboot']) 500 http://fi.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1429185 Title: Restart button in Additional Drivers does not restart Xubuntu Status in software-properties package in Ubuntu: Confirmed Bug description: After changing a driver in Additional Drivers tab of Software Updates, a message tells me a restart ('You need to restart the computer to complete the driver changes.') is needed and introduces a button to restart the system. This button does not seem to do anything in Xubuntu 14.04.2. Upon running software-properties-gtk through terminal and then clicking the restart button, these lines are printed: Traceback (most recent call last): File /usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py, line 1091, in on_driver_restart_clicked subprocess.call(['gnome-session-quit', '--reboot']) File /usr/lib/python3.4/subprocess.py, line 533, in call with Popen(*popenargs, **kwargs) as p: File /usr/lib/python3.4/subprocess.py, line 848, in __init__ restore_signals, start_new_session) File /usr/lib/python3.4/subprocess.py, line 1446, in _execute_child raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno 2] No such file or directory: 'gnome-session-quit' 'gnome-session-quit' does not work on Xubuntu with a fresh install. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: software-properties-gtk 0.92.37.3 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.340 CurrentDesktop: XFCE Date: Fri Mar 6 15:45:48 2015 LiveMediaBuild: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1429185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445595] Re: Empty Trash Results in File Windows Opening
I confirm this report. More technical information in my bug reports: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452157 ** Tags added: nautilus unity -- 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/1445595 Title: Empty Trash Results in File Windows Opening Status in Unity: New Status in nautilus package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: When selecting 'empty trash' from the launcher I get a dialog to confirm the deletion and a file window. When emptying trash from nautilus window only get confirmation dialog as expected. Expected behavior: - Only confirm dialog pop up. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1445595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447807] Re: systemctl enable shows error on enabling a SysV service
It built now in https://launchpad.net/~pitti/+archive/ubuntu/sru-test so you are welcome to test that. That's the current ubuntu packaging branch, which I'll upload as a vivid SRU as soon as I figure out bug 102. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447807 Title: systemctl enable shows error on enabling a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: In Progress Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452162] [NEW] Sound doesn't work with Praat
Public bug reported: I'm using Ubuntu 12.04 LTS on a Dell XPS13. I usually don't have any problems with sound. Now I installed the program Praat (http://www.fon.hum.uva.nl/praat/download_linux.html) version 5.3.2-1. When I want to play a sound, it doesn't work. When I open Praat via the command line and try to play a sound, I get the following error: Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, lowLatency )' failed in 'pa_linux_alsa.c', line: 415 I tried to follow the sound troubleshooting advice here: https://help.ubuntu.com/community/SoundTroubleshootingProcedure but it didn't help so far. Does anybody know why I get this error, and what I can do about it? Thank you for your help! ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1452162 Title: Sound doesn't work with Praat Status in alsa-driver package in Ubuntu: New Bug description: I'm using Ubuntu 12.04 LTS on a Dell XPS13. I usually don't have any problems with sound. Now I installed the program Praat (http://www.fon.hum.uva.nl/praat/download_linux.html) version 5.3.2-1. When I want to play a sound, it doesn't work. When I open Praat via the command line and try to play a sound, I get the following error: Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, lowLatency )' failed in 'pa_linux_alsa.c', line: 415 I tried to follow the sound troubleshooting advice here: https://help.ubuntu.com/community/SoundTroubleshootingProcedure but it didn't help so far. Does anybody know why I get this error, and what I can do about it? Thank you for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1452162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445543] Re: GTK apps on Mir: Input focus is unreliable and sporadic. Background windows ignore input and/or focus switches apparently randomly.
It's possible this is not an input or focus issue at all. It's possible GTK is failing to notify Mir of some window redraws in multi-window apps so some windows (sometimes) appear to freeze. ** Summary changed: - GTK apps on Mir: Input focus is unreliable and sporadic. Background windows ignore input and/or focus switches apparently randomly. + Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1445543 Title: Multi-window GTK apps in Mir are randomly unresponsive, seem to freeze Status in Mir: New Status in gtk+3.0 package in Ubuntu: New Bug description: GTK apps on Mir: Input focus is unreliable and sporadic. Background windows ignore input and/or focus switches apparently randomly. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1445543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444872] Re: Empty-blank space when dragging icon to panel
** Tags added: dash icons interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1444872 Title: Empty-blank space when dragging icon to panel Status in One Hundred Papercuts: Confirmed Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Ubuntu 15.04 Vivid When dragging icon to panel it's become blank icon It's also happened in 14.04 LTS in unity (backport) from proposed repo. See this video https://www.youtube.com/watch?v=5mdWKA-vReU ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Apr 16 11:42:47 2015 InstallationDate: Installed on 2015-04-12 (3 days ago) InstallationMedia: SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1444872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433761] Re: apt-key and add-apt-repository don't honor Acquire::http::Proxy
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1433761 Title: apt-key and add-apt-repository don't honor Acquire::http::Proxy Status in software-properties package in Ubuntu: Confirmed Bug description: When setting the proxy server globally on the system for the APT package manager, add-apt-repository ignores the setting. This issue is present on all versions of Debian that I have tested. # cat /etc/apt/apt.conf.d/80proxy Acquire::http::proxy http://w.x.y.z:/;; # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.TIa517Kcw8 --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring /etc/apt/trusted.gpg.d/saltstack-salt.gpg --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0 gpg: requesting key F9CB8DB0 from hkp server keyserver.ubuntu.com gpg: keyserver timed out gpg: keyserver receive failed: keyserver error This has serious repercussions. Unattended installs such as juju, maas, etc are all affected for anyone who is working behind a proxy. This is the case for most enterprise environments where such maas and juju setups will be tested out, and as such has great repercussions for Canonical as a viable supplier of OpenStack environments: if your product fails to install, you're not going to get the business. Considering that: * The setting to use already exists in /etc/apt/apt.conf and that all other tools use this correctly * The serious impact of this issue for downstream projects and Debian usage in the enterprise * The long time this issue has been standing and has affected people I suggest that this either 1) be fixed, or 2) the apt-key and add-apt-repository programs are renamed so that it is made clear they are not part of the APT suite of programs and therefor cannot be trusted to behave as if they were part of APT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1433761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452193] [NEW] Backends can't look at FINAL_CONTENT_TYPE to determine MIME type of job
Public bug reported: We have a custom cups backend (thinlocal) that looks at FINAL_CONTENT_TYPE to find out whether the submitted job is application/pdf and if so, take special actions. The PPD for this backend accepts PDF:s directly through this line: *cupsFilter: application/pdf 0 - However, FINAL_CONTENT_TYPE is always set to printer/thinlocal, so the backend can't possibly determine the input format by looking at the FINAL_CONTENT_TYPE. This is broken with (at least): - Ubuntu 14.04 (cups 1.7.2), - Ubuntu 14.10 (cups 1.7.5) - Ubuntu 15.04 (cups 2.0.2). Related bug reports, upstream and elsewhere: - https://www.cups.org/str.php?L4494 - https://bugzilla.redhat.com/show_bug.cgi?id=1010580 - https://bugzilla.redhat.com/show_bug.cgi?id=1149244 ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1452193 Title: Backends can't look at FINAL_CONTENT_TYPE to determine MIME type of job Status in cups package in Ubuntu: New Bug description: We have a custom cups backend (thinlocal) that looks at FINAL_CONTENT_TYPE to find out whether the submitted job is application/pdf and if so, take special actions. The PPD for this backend accepts PDF:s directly through this line: *cupsFilter: application/pdf 0 - However, FINAL_CONTENT_TYPE is always set to printer/thinlocal, so the backend can't possibly determine the input format by looking at the FINAL_CONTENT_TYPE. This is broken with (at least): - Ubuntu 14.04 (cups 1.7.2), - Ubuntu 14.10 (cups 1.7.5) - Ubuntu 15.04 (cups 2.0.2). Related bug reports, upstream and elsewhere: - https://www.cups.org/str.php?L4494 - https://bugzilla.redhat.com/show_bug.cgi?id=1010580 - https://bugzilla.redhat.com/show_bug.cgi?id=1149244 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1452193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447807] Re: systemctl enable shows error on enabling a SysV service
** Summary changed: - systemctl enable fails to enable a SysV service + systemctl enable shows error on enabling a SysV service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447807 Title: systemctl enable shows error on enabling a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: In Progress Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452204] [NEW] evdev device for retro-bit NES controller adapter isn't set up as a joystick
Public bug reported: Games which rely on SDL2 (and tools like antimicro) can't see the retro- bit NES controller adapter by default because SDL2 has dropped support for the old /dev/input/jsX API and udev lacks a rule to permission the /dev/input/eventX node appropriately and set the ID_INPUT_JOYSTICK flag. The following rule (or equivalent) needs to be added to the system- provided udev rules. SUBSYSTEM==input, ATTRS{name}==INNEX NES Controller USB, MODE=0666, ENV{ID_INPUT_JOYSTICK}=1 I come to this conclusion because: 1. Until the mode is changed, feeding evtest with an explicit input device number results in a permissions error. 2. Globally allowing users to read joystick input poses no security risk and the data is already mirrored via /dev/input/jsX which is 0666 already. 3. Once the mode is changed, sdl2-jstest and antimicro still cannot see it. 4. Once ID_INPUT_JOYSTICK=1 is set, sdl2-jstest and antimicro work just as well as sdl-jstest and jstest-gtk, which use the old API. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: LXDE CustomUdevRuleFiles: 99-escpos.rules 49-teensy.rules 99-nes-controller.rules 99-TrueRNG.rules Date: Wed May 6 05:39:13 2015 InstallationDate: Installed on 2014-08-01 (278 days ago) InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic root=UUID=d8313afd-996d-4d2c-9764-02e9336e03fd ro verbose SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GMA-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1452204 Title: evdev device for retro-bit NES controller adapter isn't set up as a joystick Status in systemd package in Ubuntu: New Bug description: Games which rely on SDL2 (and tools like antimicro) can't see the retro-bit NES controller adapter by default because SDL2 has dropped support for the old /dev/input/jsX API and udev lacks a rule to permission the /dev/input/eventX node appropriately and set the ID_INPUT_JOYSTICK flag. The following rule (or equivalent) needs to be added to the system- provided udev rules. SUBSYSTEM==input, ATTRS{name}==INNEX NES Controller USB, MODE=0666, ENV{ID_INPUT_JOYSTICK}=1 I come to this conclusion because: 1. Until the mode is changed, feeding evtest with an explicit input device number results in a permissions error. 2. Globally allowing users to read joystick input poses no security risk and the data is already mirrored via /dev/input/jsX which is 0666 already. 3. Once the mode is changed, sdl2-jstest and antimicro still cannot see it. 4. Once ID_INPUT_JOYSTICK=1 is set, sdl2-jstest and antimicro work just as well as sdl-jstest and jstest-gtk, which use the old API. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.11 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: LXDE CustomUdevRuleFiles: 99-escpos.rules 49-teensy.rules 99-nes-controller.rules 99-TrueRNG.rules Date: Wed May 6 05:39:13 2015 InstallationDate: Installed on 2014-08-01 (278 days ago) InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-USB3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-48-generic root=UUID=d8313afd-996d-4d2c-9764-02e9336e03fd ro verbose SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-880GMA-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
[Touch-packages] [Bug 1377872] Re: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel
Incomplete. It appears we're both experiencing just bug 1447896 now. Bug 1377872 hasn't definitely been seen since late-2014. ** Changed in: mir Status: Confirmed = Incomplete ** Changed in: mesa (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377872 Title: Double-buffered compositing performance is sometimes very poor (30 FPS) on intel Status in Mesa: Confirmed Status in Mir: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: Double-buffered compositing performance is sometimes artificially poor on some intel systems. When this happens the frame rate seen is halved - about 30 FPS. However at the same time, Mir is observed to use very little render time and both the CPU and GPU are still mostly idle. It's just the Intel DRM logic sometimes takes two frames (~32ms) to complete a single page flip. Two known workarounds avoid the issue: (a) Add glFinish() into the mesa DisplayBuffer code; or (b) env INTEL_DEBUG=sync for the Mir server binary. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1377872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451024] Re: Ubuntu phone: Changed (dpi?) resolution in the last core update
** Attachment added: messenger.png https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1451024/+attachment/4392084/+files/messenger.png ** Changed in: oxide-qt (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1451024 Title: Ubuntu phone: Changed (dpi?) resolution in the last core update Status in oxide-qt package in Ubuntu: Incomplete Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Hi! After the last core update, 2 weeks ago, a few webapps have problems with the resolution. By example 'messenger' and 'the circle game'. Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1451024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452211] [NEW] Wizard crashes when viewing HERE terms and conditions
You have been subscribed to a public bug: Test case. 1. During the wizard, switch to Spanish. 2. Fill wifi credentials. 3. In Term Conditions, tap to read the HERE terms. 4. In this screen tap in the URL of the HERE terms. 5. Go back to main Term Conditions. 6. Repeat steps 3 to 5. Expected result. - No crash. Actual result. - Unity crashes and reboots. current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: qa-regression -- Wizard crashes when viewing HERE terms and conditions https://bugs.launchpad.net/bugs/1452211 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451024] Re: Ubuntu phone: Changed (dpi?) resolution in the last core update
Thanks for the report Marcos. Could you please elaborate on what you mean by problems with the resolution? I’m attaching two screenshots of how the circle game and messenger app look like on my BQ running the latest devel-proposed image (which has oxide 1.7.7). Does this look different on RTM? Or does it look similar, but are you expecting something different? ** Attachment added: circle-game-devel.png https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1451024/+attachment/4392083/+files/circle-game-devel.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1451024 Title: Ubuntu phone: Changed (dpi?) resolution in the last core update Status in oxide-qt package in Ubuntu: Incomplete Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Hi! After the last core update, 2 weeks ago, a few webapps have problems with the resolution. By example 'messenger' and 'the circle game'. Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1451024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452180] [NEW] /usr/bin/telephony-service-indicator:11:QString:Tp::Contact::id:CallChannelObserver::onCallStateChanged:CallChannelObserver::qt_static_metacall:QMetaObject::activa
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding telephony-service. This problem was most recently seen with version 0.1+15.04.20150421-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9195c26bd43c96746c7ff8f5c9ca4c04685a1801 contains more details. ** Affects: telephony-service (Ubuntu) Importance: Undecided Status: New ** Tags: rtm-14.09 vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1452180 Title: /usr/bin/telephony-service- indicator:11:QString:Tp::Contact::id:CallChannelObserver::onCallStateChanged:CallChannelObserver::qt_static_metacall:QMetaObject::activate Status in telephony-service package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding telephony-service. This problem was most recently seen with version 0.1+15.04.20150421-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9195c26bd43c96746c7ff8f5c9ca4c04685a1801 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1452180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450332] Re: Xorg freeze
If I understand correctly the web page referred to above, I should: sudo apt-get install --install-recommends linux-generic-lts-utopic xserver-xorg-lts-utopic libgl1-mesa-glx-lts-utopic libegl1-mesa-drivers-lts-utopic I'm reluctant to do this, as the web page does not state the reversion method in case of problems. What is it? It also says that I can check the hwe support status by: hwe-support-status --verbose However, when I do that, the command is not found. Synaptic says that there is no package similar to that command's name. What is the relevant package's name? -- 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/1450332 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Switching user (i.e. using hotspot at top right of screen) results in a blank screen. Not sure which package this applies to. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18 Uname: Linux 3.13.0-51-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 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: Thu Apr 30 07:53:20 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-49-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-51-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2014-04-25 (369 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Gigabyte Tecohnology Co., Ltd. H61M-S2PV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-51-generic root=UUID=0d248ee7-6e51-4cfd-aa7e-f1963792d493 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-S2PV dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Tecohnology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd12/19/2011:svnGigabyteTecohnologyCo.,Ltd.:pnH61M-S2PV:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61M-S2PV:rvrTobefilledbyO.E.M.:cvnGigabyteTecohnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H61M-S2PV dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Tecohnology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Apr 30 07:50:00 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 39446 vendor XER xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1450332/+subscriptions -- Mailing list: https://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 1450790] Re: Phone not connecting to mobile data until rebooting
On 06.05.2015 02:30, Tony Espy wrote: 1. You're roaming, and have enabled data roaming Yes, I've been in London for the weekend. I bought a 1 week international data flat. Anyhow, I can still reproduce this 100% now that I'm back home. 2. At times ( 14:11, 15:30, 22:29, 22:35 - 23:14 ) it looks like you have poor cell reception as your phone is dropping of GPRS quite a bit, and usually when the phone re-attaches, NM fails to activate context1 every time, and the error is 'no-secrets'. Note, GPRS detaching and re- attaching usually means you're losing a connection from your operator, but as we don't log operator registration itself, I can't tell if it's just GPRS that's dropping. Looks like the times I entered metro stations :) So yes... Basically I had to reboot every time after I exited the metro, because cell reception dropped, mobile data disconnected and wouldn't reconnect until rebooting. 3. The only time NM succeeds activating context1 is after reboots, which I can see from your syslog. yep, exactly. 4. Are you aware that your phone tried to attach to a LasarJet printer?? ;)- Yeah, I think I tapped that in order to force the list to update as it wouldn't show the hotel network for a while after being back in the hotel. But that's a different (not so critical) issue. Finally, I think this may be related to bug #1435776 as it deals with an APN with 'Username', but no 'Password', but that's just because both involve secrets. Can't judge that. Please let me know if I can provide more logs/details/testing. We really need to get this nailed down as it's the most important thing on a phone after being able to do voice calls. -- 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/1450790 Title: Phone not connecting to mobile data until rebooting Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: New Status in ofono package in Ubuntu: New Bug description: Whenever I walk out of WiFi range, my phone does not connect to mobile data. Toggling flight mode does not help. I have to reboot the phone. When then I finally manage to connect after rebooting, if the signal strength drops and the phone would want to switch from 3G to 2G, it disconnects and I have to reboot again to get mobile data. $ system-image-cli -i current build number: 200 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-30 11:07:21 version version: 200 version ubuntu: 20150429 version device: 20150326-f0c5ba5 version custom: 20150429 Attached you'll find the output of the forensics script To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1193822] Re: dh-migrations: Typo in package description: packaged
** Branch linked: lp:~reversiblean/session-migration/session-migration -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to session-migration in Ubuntu. https://bugs.launchpad.net/bugs/1193822 Title: dh-migrations: Typo in package description: packaged Status in Package Descriptions for Ubuntu (to make translation easy): Triaged Status in session-migration package in Ubuntu: In Progress Bug description: Package: dh-migrations Version: 0.2 Hello, There's a typo in string #911 in the following sentence: ...operations on the installed packaged. (packaged should be replaced with packages) Link: https://translations.launchpad.net/ddtp-ubuntu/raring/+pots /ddtp-ubuntu-main/fr/911 Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1193822/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444402] Re: While sbuilding in LXC, systemd loops attempting to umount the underlay
** Changed in: systemd (Ubuntu) Milestone: vivid-updates = None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/102 Title: While sbuilding in LXC, systemd loops attempting to umount the underlay Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Vivid: In Progress Bug description: I recently hit ENOSPC which turned out to be the result of various syslogs from the current and previous boots totalling up to 30G. They were filled with messages like Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid umount[31795]: umount: /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734: target is busy Apr 15 11:22:35 vivid umount[31795]: (In some cases useful info about processes that Apr 15 11:22:35 vivid umount[31795]: use the device is found by lsof(8) or fuser(1).) Apr 15 11:22:35 vivid systemd[1]: var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount mount process exited, code=exited status=32 Apr 15 11:22:35 vivid systemd[1]: Failed unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid systemd[1]: Unmounted /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount entered failed state. looping constantly for the duration of any builds in sbuild. Why is systemd trying to do this? laney@vivid apt-cache policy systemd systemd: Installed: 219-7ubuntu1 Candidate: 219-7ubuntu1 Version table: *** 219-7ubuntu1 0 500 http://sherwood/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382283] Re: wifi toggle interrupts sound playback
I opened a new one against barajas, thanks. https://bugs.launchpad.net/barajas/+bug/1452128 -- 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/1382283 Title: wifi toggle interrupts sound playback Status in network-manager package in Ubuntu: Invalid Bug description: Not really sure where this bug should go, but on recent rtm krillin images (such as 112), turning wifi on/off in the network indicator causes a brief interruption in music playback. Steps to reproduce the issue: 1. Start playing a song in the music app. 2. Pull down the network indicator. 3. Toggle wi-fi on or off. For some reason, this makes the sound pause for a moment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1382283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449647] Re: screen flickering during fullscreen video playback
skt.diaz, could you please report this to AMD directly following https://help.ubuntu.com/community/BinaryDriverHowto/AMD#Reporting_a_bug_in_fglrx_when_using_latest_upstream_beta_and_stable_downloaded_directly_from_AMD.27s_website ? ** Package changed: xorg (Ubuntu) = fglrx-installer (Ubuntu) ** Changed in: fglrx-installer (Ubuntu) Status: Incomplete = Triaged ** Also affects: fglrx 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/1449647 Title: screen flickering during fullscreen video playback Status in AMD fglrx video driver: New Status in fglrx-installer package in Ubuntu: Triaged Bug description: When I adjust the brightness or volume using the keyboard media buttons during full screen video playback, the screen flickers. This happens in both Vlc and the default Videos application. Is there a fix for this? I am using ubuntu 15.04 with ati catalyst 15.20. this doesnt happen when i am not using fullscreen playback. its probably associated with the notifications that come up on pressing the volume or brightness buttons. WORKAROUND: Use the default radeon driver. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: fglrx wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 28 21:29:46 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-15-generic, x86_64: installed fglrx-updates-core, 15.200, 3.19.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0447] InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=ca46178c-fd77-4461-9b43-9e789460d778 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.board.version: A15 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A15 dmi.modalias: dmi:bvnDellInc.:bvrA15:bd07/19/2011:svnDellInc.:pnInspironN5010:pvrA15:rvnDellInc.:rn:rvrA15:cvnDellInc.:ct8:cvrA15: dmi.product.name: Inspiron N5010 dmi.product.version: A15 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Apr 28 19:26:13 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1449647/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5
I send and receive mms without problem here in Switzerland (operator Sunrise). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1439101 Title: impossible receive MMS any operator on bq aquaris E4.5 Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu Mobile: New Status in messaging-app package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition For information, my operator is Free even if it seems it doesn't matter. In the same time, let me tell you than I had detect than MMS didn't sent when WIFI is ON. I've read some other people who send the same information so it's seems to be a real bug. Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if ON, and in all of case we don't receive MMS :-(( Thank's to you for fix it faster. Sorry for my approximativ english. Fabien To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446809] Re: denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Changed in: openldap (Debian) Status: Unknown = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1446809 Title: denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) Status in openldap package in Ubuntu: New Status in openldap package in Debian: Fix Released Bug description: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] TBD [Other Info] * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 have to agree Rob. Having python3-venv as a new and separate package makes it only confusing for developers. I could live with this, if the package would be a dependency of python3, so it gets installed automatically. -- 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 1447955] Re: [systemd] package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
This was apparently fixed in vivid's invoke-rc.d, i. e. considering the case that a package only has an upstart job and a systemd unit, but no init.d script. apt-get install modemmanager is fine in vivid, so this invoke-rc.d fix would need to get backported to utopic. ** Summary changed: - [systemd] package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 + package modemmanager 1.4.0-1 failed to install/upgrade: invoke-rc.d fails on missing init.d script -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1447955 Title: package modemmanager 1.4.0-1 failed to install/upgrade: invoke-rc.d fails on missing init.d script Status in modemmanager package in Ubuntu: Confirmed Bug description: This bug is reproduced during upgrade from 14.10 to 15.04. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: modemmanager ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri Apr 24 09:00:25 2015 DuplicateSignature: package:modemmanager:1.4.0-1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2014-12-09 (135 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: modemmanager Title: package modemmanager 1.4.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1447955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452098] Re: [Launcher]home button can not setcurrentscope as you want
Sorry but i don't understand what the problem is, can you please try to rephrase it in a more step by step saying what happens and what you would expect to happen? ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1452098 Title: [Launcher]home button can not setcurrentscope as you want Status in unity8 package in Ubuntu: Incomplete Bug description: every time you click home button it will show you clickscope, when you swipe to another scope,for example video, you click home button, you should be shown clickscope as code want (in shell.qml, there is a function showHome() and a line code dash.setCurrentScope(),you can change arguments you want), but only focused unity8-dash, in an interesting condition ,when you runs unity8 and unity8-dash with qtcreator, everything works fine, maybe it means the function of setCurrentScope() has some trouble; what i can see in unity8.log may be about to this condition is below: UbuntuClipboard - Failed to get system clipboard contents via D-Bus. org.freedesktop.DBug.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 xepired, or the network connections was broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1452098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444402] Re: While sbuilding in LXC, systemd loops attempting to umount the underlay
Simpler reproducer: - Create a vivid container, and set lxc.aa_profile = unconfined - Start the container - Run mount -v -o bind /bin /mnt Mai 06 09:17:08 test systemd[1]: Unit mnt.mount is bound to inactive unit dev-sda3.device. Stopping, too. Mai 06 09:17:08 test systemd[1]: Unmounting /mnt... Mai 06 09:17:08 test systemd[1]: Unmounted /mnt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/102 Title: While sbuilding in LXC, systemd loops attempting to umount the underlay Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Vivid: In Progress Bug description: I recently hit ENOSPC which turned out to be the result of various syslogs from the current and previous boots totalling up to 30G. They were filled with messages like Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid umount[31795]: umount: /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734: target is busy Apr 15 11:22:35 vivid umount[31795]: (In some cases useful info about processes that Apr 15 11:22:35 vivid umount[31795]: use the device is found by lsof(8) or fuser(1).) Apr 15 11:22:35 vivid systemd[1]: var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount mount process exited, code=exited status=32 Apr 15 11:22:35 vivid systemd[1]: Failed unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount is bound to inactive unit dev-disk-by\x2duuid-980689ca\x2de7d9\x2d4a99\x2d8230\x2d33b8b6e917cd.device. Stopping, too. Apr 15 11:22:35 vivid systemd[1]: Unmounting /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734... Apr 15 11:22:35 vivid systemd[1]: Unmounted /var/lib/schroot/union/underlay/vivid-amd64-5d4f7453-9a95-4a6a-9aee-9394923bf734. Apr 15 11:22:35 vivid systemd[1]: Unit var-lib-schroot-union-underlay-vivid\x2damd64\x2d5d4f7453\x2d9a95\x2d4a6a\x2d9aee\x2d9394923bf734.mount entered failed state. looping constantly for the duration of any builds in sbuild. Why is systemd trying to do this? laney@vivid apt-cache policy systemd systemd: Installed: 219-7ubuntu1 Candidate: 219-7ubuntu1 Version table: *** 219-7ubuntu1 0 500 http://sherwood/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449555] Re: password request for cryptswap1 during boot when encrypted home directory selected
*** This bug is a duplicate of bug 1447282 *** https://bugs.launchpad.net/bugs/1447282 I can confirm I have the same issue after the upgrade from Ubuntu GNOME 14.04.2 LTS to Ubuntu GNOME 15.04. Anyone knows a workaround for this? Do you need any logs or conf files to confirm/resolve it? I can provide if needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1449555 Title: password request for cryptswap1 during boot when encrypted home directory selected Status in systemd package in Ubuntu: Triaged Bug description: On a system freshly installed (haven't tried the upgrade route) where the user selects to encrypt their home directory, they will get a password prompt during boot and at other times on the command-line requesting a password for cryptswap1. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: cryptsetup 2:1.6.1-1ubuntu7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 28 09:02:12 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-28 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) crypttab: cryptswap1 UUID=c9d10691-df3f-49ae-a734-cdf2cbbaee8e /dev/urandom swap,offset=1024,cipher=aes-xts-plain64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449555/+subscriptions -- Mailing list: https://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 1452211] Re: Wizard crashes when viewing HERE terms and conditions
How can I know whether it is the same issue or not? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1452211 Title: Wizard crashes when viewing HERE terms and conditions Status in unity8 package in Ubuntu: Incomplete Bug description: Test case. 1. During the wizard, switch to Spanish. 2. Fill wifi credentials. 3. In Term Conditions, tap to read the HERE terms. 4. In this screen tap in the URL of the HERE terms. 5. Go back to main Term Conditions. 6. Repeat steps 3 to 5. Expected result. - No crash. Actual result. - Unity crashes and reboots. current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1452211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433761] Re: apt-key and add-apt-repository don't honor Acquire::http::Proxy
This is a very annoying bug that hits me very often. It's also the source of yet another place to configure the proxy server. My usual work around is trying to patch all executions of apt-key and friends to use --keyserver-options http-proxy=$http_proxy. It might be possible to patch /root/.gnupg/gpg.conf to include that setting, but I haven't tried that yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1433761 Title: apt-key and add-apt-repository don't honor Acquire::http::Proxy Status in software-properties package in Ubuntu: Confirmed Bug description: When setting the proxy server globally on the system for the APT package manager, add-apt-repository ignores the setting. This issue is present on all versions of Debian that I have tested. # cat /etc/apt/apt.conf.d/80proxy Acquire::http::proxy http://w.x.y.z:/;; # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0 Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --homedir /tmp/tmp.TIa517Kcw8 --no-auto-check-trustdb --trust-model always --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-squeeze-stable.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring /etc/apt/trusted.gpg.d/saltstack-salt.gpg --keyserver keyserver.ubuntu.com --recv-keys 5A9A06AEF9CB8DB0 gpg: requesting key F9CB8DB0 from hkp server keyserver.ubuntu.com gpg: keyserver timed out gpg: keyserver receive failed: keyserver error This has serious repercussions. Unattended installs such as juju, maas, etc are all affected for anyone who is working behind a proxy. This is the case for most enterprise environments where such maas and juju setups will be tested out, and as such has great repercussions for Canonical as a viable supplier of OpenStack environments: if your product fails to install, you're not going to get the business. Considering that: * The setting to use already exists in /etc/apt/apt.conf and that all other tools use this correctly * The serious impact of this issue for downstream projects and Debian usage in the enterprise * The long time this issue has been standing and has affected people I suggest that this either 1) be fixed, or 2) the apt-key and add-apt-repository programs are renamed so that it is made clear they are not part of the APT suite of programs and therefor cannot be trusted to behave as if they were part of APT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1433761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452255] Re: Xorg freeze - on lockscreen
** Attachment added: Shuold show what I updated after the boot (but not still in effect) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1452255/+attachment/4392194/+files/dpkg.log.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1452255 Title: Xorg freeze - on lockscreen Status in xorg package in Ubuntu: New Bug description: What I know for sure: Locked screen - machine was frozen when I got back after minutes/seconds. Has happened several times before but does not happen most/all of the time. Of course very annoying (so I'll switch from nouveau to propriatary as a desperate move.. I really do not want to, would rather file bugs and see them fixed. Filing is what I can do, do not trust myself to fix or debug as random. I may move back if it helps with debugging). I wouldn't have thought Xorg was to blame (maybe it isn't) as machine only freezes this way when I lock screen (yes, I get oom for chrome and almost freezes, but can get to a virtual terminal - eventually, but that is different). Also I've reported other bug about lockscreen where password field if missing. This seems unrelated as here it is not. In hte other bug the mouse pointer may not have been frozen (I can't remember for sure). [I have dual-screen, not sure if important - seemed to be for other bug..] CAPS LOCK etc. lights are frozen and can't go to virtual screen. Still FLock light toggles, I think only the keyboard handles that.. Going over updates not installed, nothing important seems missing (as the update-manager shows *now*), I frequently do not update everything. E.g. libdrm-intel1 should not matter, I updated nouveau version recently: 2015-04-21 13:47:52 status installed libdrm-nouveau2:amd64 2.4.60-2~ubuntu14.04.1 and booted before getting the freeze but at least this was updated but not rebooted before the freeze: 2015-05-04 09:35:32 upgrade libmetacity-private0a:amd64 1:2.34.13-0ubuntu4 1:2.34.13-0ubuntu4.1 2015-05-04 09:35:33 upgrade metacity-common:all 1:2.34.13-0ubuntu4 1:2.34.13-0ubuntu4.1 Last rebootprior to freeze(?): $ who -b /var/log/wtmp.1 |tail -1 system boot 2015-04-28 14:11 While I get no response to (other) keys, I see that the kernel sees them in syslog (all relevant there starting w/nouveau):. May 6 09:55:01 Vinnuryksugan CRON[14155]: (root) CMD (command -v debian-sa1 /dev/null debian-sa1 1 1) May 6 10:05:01 Vinnuryksugan CRON[14305]: (root) CMD (command -v debian-sa1 /dev/null debian-sa1 1 1) May 6 10:10:27 Vinnuryksugan kernel: [677054.614186] nouveau E[compiz[2344]] fail ttm_validate May 6 10:10:27 Vinnuryksugan kernel: [677054.614191] nouveau E[compiz[2344]] validate vram_list May 6 10:10:27 Vinnuryksugan kernel: [677054.614201] nouveau E[compiz[2344]] validate: -12 May 6 10:10:28 Vinnuryksugan kernel: [677055.299662] nouveau E[ PFIFO][:01:00.0] read fault at 0x000774 [PAGE_NOT_PRESENT] from PGRAPH/GPC0/TEX on channel 0x001fcba000 [compiz[2344]] May 6 10:10:28 Vinnuryksugan kernel: [677055.299688] nouveau E[ PGRAPH][:01:00.0] TRAP ch 4 [0x001fcba000 compiz[2344]] May 6 10:10:28 Vinnuryksugan kernel: [677055.299699] nouveau E[ PGRAPH][:01:00.0] GPC0/TPC0/TEX: 0x8049 May 6 10:10:28 Vinnuryksugan kernel: [677055.299703] nouveau E[ PGRAPH][:01:00.0] GPC0/TPC1/TEX: 0x8049 May 6 10:12:01 Vinnuryksugan CRON[14409]: (root) CMD (export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin [ -x /usr/sbin/uptrack-upgrade ] /usr/sbin/uptrack-upgrade --cron) May 6 10:12:09 Vinnuryksugan kernel: [677156.263221] nouveau E[Xorg[1177]] failed to idle channel 0x0001 [Xorg[1177]] May 6 10:12:24 Vinnuryksugan kernel: [677171.270132] nouveau E[Xorg[1177]] failed to idle channel 0x0001 [Xorg[1177]] May 6 10:12:26 Vinnuryksugan kernel: [677173.271187] nouveau E[ PFIFO][:01:00.0] playlist update failed May 6 10:12:41 Vinnuryksugan kernel: [677188.277961] nouveau E[Xorg[1177]] failed to idle channel 0x [Xorg[1177]] May 6 10:12:56 Vinnuryksugan kernel: [677203.284882] nouveau E[Xorg[1177]] failed to idle channel 0x [Xorg[1177]] May 6 10:12:58 Vinnuryksugan kernel: [677205.285829] nouveau E[ PFIFO][:01:00.0] channel 2 [Xorg[1177]] kick timeout May 6 10:12:58 Vinnuryksugan kernel: [677205.286008] nouveau W[ PFIFO][:01:00.0] INTR 0x0100: 0x000d May 6 10:13:00 Vinnuryksugan kernel: [677207.286827] nouveau E[ PFIFO][:01:00.0] playlist update failed May 6 10:13:04 Vinnuryksugan colord: device removed: xrandr-Dell Inc.-DELL P2312H-YJ3JX33IAFJM May 6 10:13:04 Vinnuryksugan colord: device removed: xrandr-Dell Inc.-DELL P2312H-YJ3JX33IAF8M May 6 10:13:04 Vinnuryksugan colord: Profile removed:
[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops
** Changed in: canonical-devices-system-image Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Fix Committed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452227] Re: do-release-upgrade from utopic to vivid failed with Python unicode error
Preparing to unpack .../systemd_219-7ubuntu4_amd64.deb ... sh: echo: I/O error dpkg: error processing archive /var/cache/apt/archives/systemd_219-7ubuntu4_amd64.deb (--unpack): This is most probably a hardware problem, can you please check dmesg for some relevant messages? Perhaps you also have a full disk, but then the error message should say that. ** Package changed: systemd (Ubuntu) = ubuntu ** Changed in: ubuntu Status: New = Incomplete ** Summary changed: - do-release-upgrade from utopic to vivid failed with Python unicode error + unpacking deb fails with I/O error -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1452227 Title: unpacking deb fails with I/O error Status in Ubuntu: Incomplete Bug description: I was upgrading from utopic to vivid, using do-release-upgrade and all was fine until this Python unicode error, and then my system was left in an unusable state. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 Date: Wed May 6 11:41:16 2015 DuplicateSignature: package:systemd:208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2012-10-24 (923 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) SourcePackage: systemd Title: package systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1452227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452238] [NEW] Failed to upgrade system from 14.04
Public bug reported: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: ifupdown Importance: Undecided Status: New ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: ifupdown Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430694] Re: Update Facebook permissions to 2.0 API
I tested it in utopic-proposed and it works fine. Note that I didn't test this in trusty-proposed (the package has not been uploaded there yet), but anyway I don't expect it to be any different there. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1430694 Title: Update Facebook permissions to 2.0 API Status in Online Accounts: Account plugins: In Progress Status in the base for Ubuntu mobile products: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in account-plugins source package in Trusty: New Status in account-plugins source package in Utopic: Fix Committed Status in account-plugins package in Ubuntu RTM: Fix Released Bug description: The 1.0 API is being deprecated on April 30, 2015. [Impact] Depending on how facebook decides to handle the deprecation, there's the possibility that creating facebook accounts from Ubuntu Online Accounts will just stop working, if our OAuth request (which uses deprecated parameters) gets declined. [Test case] Until the deprecation actually takes place, we won't be able to reproduce the bug. According to the Facebook official documentation, the v1.0 API will stop working on April 30th, 2015: https://developers.facebook.com/docs/apps/changelog [Regression potential] Very low: the new Facebook v2.0 API is already active, and we've been using it in Vivid without issues. A quick smoke test (just create a Facebook account from the System Settings - Online Accounts pane) is anyway advised, to be absolutely sure. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1430694/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452227] [NEW] do-release-upgrade from utopic to vivid failed with Python unicode error
Public bug reported: I was upgrading from utopic to vivid, using do-release-upgrade and all was fine until this Python unicode error, and then my system was left in an unusable state. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 Date: Wed May 6 11:41:16 2015 DuplicateSignature: package:systemd:208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2012-10-24 (923 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) SourcePackage: systemd Title: package systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-05-06 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1452227 Title: do-release-upgrade from utopic to vivid failed with Python unicode error Status in systemd package in Ubuntu: New Bug description: I was upgrading from utopic to vivid, using do-release-upgrade and all was fine until this Python unicode error, and then my system was left in an unusable state. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 Date: Wed May 6 11:41:16 2015 DuplicateSignature: package:systemd:208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2012-10-24 (923 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) SourcePackage: systemd Title: package systemd 208-8ubuntu8.2 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1452227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452211] Re: Wizard crashes when viewing HERE terms and conditions
I have no idea, anyway let's assign it to system settings since it's what is crashing. ** Changed in: unity8 (Ubuntu) Status: Incomplete = New ** Package changed: unity8 (Ubuntu) = ubuntu-system-settings (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1452211 Title: Wizard crashes when viewing HERE terms and conditions Status in ubuntu-system-settings package in Ubuntu: New Bug description: Test case. 1. During the wizard, switch to Spanish. 2. Fill wifi credentials. 3. In Term Conditions, tap to read the HERE terms. 4. In this screen tap in the URL of the HERE terms. 5. Go back to main Term Conditions. 6. Repeat steps 3 to 5. Expected result. - No crash. Actual result. - Unity crashes and reboots. current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1452211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1451613 Title: Unity/compiz crashes when locking screen Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452238] Re: Failed to upgrade system from 14.04
I had this issue on a new ARM board over the weekend too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452238] Re: Failed to upgrade system from 14.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ifupdown (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447807] Re: systemctl enable shows error on enabling a SysV service
Tested and confirmed working, thanks again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1447807 Title: systemctl enable shows error on enabling a SysV service Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Vivid: In Progress Status in systemd source package in Wily: Fix Committed Bug description: SRU TEST CASE: -- Trying to enable a SysV init service which does not have a corresponding systemd unit results in an error: # systemctl enable pulseaudio Synchronizing state for pulseaudio.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d pulseaudio defaults Executing /usr/sbin/update-rc.d pulseaudio enable Failed to execute operation: No such file or directory /etc/init.d/pulseaudio actually does get enabled (check /etc/rc*/*pulse*), but the command fails with code 1 and you get that error message. With the fix the command succeeds. SRU Regression potential Low, the modes for sysv script + systemd unit as well as systemd unit only already have automatic tests, and now this scenario (sysv script only) has a test too. In the worst case this has the potential of completely breaking systemctl enable/disable, which can be worked around with changing symlinks manually, and isn't breaking the boot. Version details: Description: Ubuntu 15.04 Release: 15.04 systemd: Installed: 219-7ubuntu3 Candidate: 219-7ubuntu3 Version table: *** 219-7ubuntu3 0 500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452244] [NEW] Xorg does not work properly after suspend
Public bug reported: When woken up from suspend (either manually or by opening the lid), xorg will not display the screen properly: The frames will be shown, but text and buttons won't until a mouse over or new text is written. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Wed May 6 13:21:34 2015 InstallationDate: Installed on 2015-04-26 (9 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Release amd64 (20150422.1) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1452244 Title: Xorg does not work properly after suspend Status in xorg package in Ubuntu: New Bug description: When woken up from suspend (either manually or by opening the lid), xorg will not display the screen properly: The frames will be shown, but text and buttons won't until a mouse over or new text is written. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Wed May 6 13:21:34 2015 InstallationDate: Installed on 2015-04-26 (9 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Release amd64 (20150422.1) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1452244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445542] Re: Using the Mir backend, secondary windows of GTK apps open behind the primary window
** Changed in: gtk+3.0 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1445542 Title: Using the Mir backend, secondary windows of GTK apps open behind the primary window Status in Mir: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Using the Mir backend, secondary windows of GTK apps open behind the primary window. This is odd because Mir's default behaviour is to put any new surface on top. e.g. Remmina (after you apply the fix for bug 1444132) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1445542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311403] Re: Can't type password after resume.
*** This bug is a duplicate of bug 1311316 *** https://bugs.launchpad.net/bugs/1311316 This is still present in 15.04. i.e. the password dialogue box is present on the lock screen but keyboard input results in no dots appearing. It is not just a case of no dots being displayed because typing the full password and pressing return has no effect. This is listed as a possible duplicate of bug #1311316 but this may not be the case as that bug seems concerned with the lack of password box being displayed and maybe dual monitors. NOTE In my case, if an onscreen touch keyboard is used, a password can be entered suggesting an issue with reactivating the keyboard following resume. -- 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/1311403 Title: Can't type password after resume. Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I couldn't type password after resume - no characters displayed this time. I had to Ctrl+alt+f2 and service lightdm restart. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Tue Apr 22 17:37:49 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (150 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301979] Re: says tested when it means recommended
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1301979 Title: says tested when it means recommended Status in software-properties package in Ubuntu: Confirmed Bug description: ./softwareproperties/gtk/SoftwarePropertiesGtk.py: if driver_status == 'recommended': base_string = _({base_description} ({licence}, tested)) That's wrong. ubuntu-drivers-common does not have a concept of tested vs untested, that was from the Jockey era where we allowed third-party repositories. recommended is for telling the user which of the umpteen NVidia versions she should pick (we don't need the flag for any other driver). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1301979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452238] Re: Failed to upgrade system from 14.04
Running apt-get install -f does: $ sudo apt-get install -f ... The following packages will be upgraded: libc-dev-bin libc6-dbg libc6-dev udev -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 64131] Re: software sources dialogue missing accels
The dialog is navigable from the keyboard; tab/shift-tab and arrow keys jump between the different fields, and space toggles the checkbox for the field you're on. I'm unconvinced that anything more is required. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/64131 Title: software sources dialogue missing accels Status in software-properties package in Ubuntu: Confirmed Bug description: Binary package hint: update-manager The Software updates dialogue [http://ubuntu- ca.org/softwaresources.png] is missing accelerators on the checkboxes and the Download from label. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/64131/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
ACK on the debdiff in comment #20. Uploaded for processing by the SRU team. Thanks! ** Changed in: rsyslog (Ubuntu Trusty) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: In Progress Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: In Progress Bug description: [rsyslog impact] This bug prevents rsyslog from receiving all events from other services on trusty when the utopic-hwe (and newer) kernels are used. The rsyslog SRU adds an additional permission (read access to /dev/log) to the rsyslog apparmor policy to allow this to work. [rsyslog test case] (1) Ensure the rsyslog apparmor policy is set to enforce; it should show up listed in the XX profiles are in enforce mode. section reported by sudo aa-status (if it's disabled, do sudo aa-enforce rsyslogd). (2) Install the utopic or newer hwe enablement stack reboot into the kernel. Using the logger(1) utility should generate log messages (e.g. logger foo) that are recorded in syslog; with this bug, they will be blocked (grep DENIED /var/log/syslog). [rsyslog regression potential] The only change to rsyslog in the SRU is a slight loosening of the rsyslog apparmor policy. The risk of an introduced regression is small. [rsyslog addition info] The qa-regression-testing script is useful for verifying that rsyslog is still functioning properly (http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-rsyslog.py) [Original description] I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448775] Re: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash
Since Compiz is a victim of bad microcode, I'm going to mark this Invalid. I'm glad you were able to track down the offending package. If you feel compelled to get intel-microcode fixed, please open a new bug report against that package. Thanks! ** Changed in: compiz Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- 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/1448775 Title: Unable to login after upgrade from 14.10 to 15.04 possible XOrg crash Status in Compiz: Invalid Status in unity package in Ubuntu: Invalid Bug description: After upgrade from working machine with 14.10 to 15.10 I'm unable to login. Right after password screen I see loading of desktop and I'm returned to password prompt again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,imgpng,unitymtgrabhandles,move,compiztoolbox,place,grid,wall,vpswitch,regex,resize,gnomecompat,snap,session,animation,expo,workarounds,ezoom,fade,scale,unityshell] Date: Sun Apr 26 23:07:55 2015 DistUpgraded: 2015-04-26 22:20:44,130 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26: added EcryptfsInUse: Yes ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GT218M [GeForce 315M] [10de:0a7a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems GeForce 315M [1179:fd71] InstallationDate: Installed on 2014-11-07 (170 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA SATELLITE C670-10V ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=28cea712-ba61-42af-a038-545501a067f8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to vivid on 2015-04-26 (0 days ago) dmi.bios.date: 04/20/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: TKBSC dmi.board.vendor: TOSHIBA dmi.board.version: 1.40 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd04/20/2011:svnTOSHIBA:pnSATELLITEC670-10V:pvrPSC3QE-00700JPL:rvnTOSHIBA:rnTKBSC:rvr1.40:cvnTOSHIBA:ct9:cvrToBeFilledByO.E.M.: dmi.product.name: SATELLITE C670-10V dmi.product.version: PSC3QE-00700JPL dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 26 23:07:32 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1448775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446809] Re: denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Description changed: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] TBD [Other Info] - + * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html + * Patches backported: + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) Status in openldap package in Ubuntu: New Status in openldap package in Debian: Fix Released Bug description: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] TBD [Other Info] * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html * Patches backported: - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446809] Re: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Description changed: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] - TBD + * this set of patches adds validations to avoid segfaults, so no + regression is expected. [Other Info] * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html * Patches backported: - - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) - - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) - - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) Status in openldap package in Ubuntu: New Status in openldap package in Debian: Fix Released Bug description: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] * this set of patches adds validations to avoid segfaults, so no regression is expected. [Other Info] * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html * Patches backported: - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446809] Re: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Patch added: lp1446809_precise.debdiff https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+attachment/4392199/+files/lp1446809_precise.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) Status in openldap package in Ubuntu: New Status in openldap package in Debian: Fix Released Bug description: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] * this set of patches adds validations to avoid segfaults, so no regression is expected. [Other Info] * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html * Patches backported: - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401842] Re: Two cursors on each tty console
Here we go for the development version. If you need the data from a trusty version, please let me know. ** Attachment added: xorg.apport https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1401842/+attachment/4392200/+files/xorg.apport -- 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/1401842 Title: Two cursors on each tty console Status in xorg package in Ubuntu: Incomplete Bug description: Package: xorg Version: 1:7.7+1ubuntu8 How to reproduce: 1) Make sure you have X and gpm running. Observe that under X you are having just one cursor displayed. 2) Press Ctrl+Alt+F1 to switch to tty1 console. 3) Observe that you have two cursors on the black screen: the square one is probably from gpm and responds to mouse movements, while the arrow one is as in X, is centered, and it does not move with the mouse. The screen foto is attached. Expected: exactly one cursor under X, exactly one cursor on each console, both X and console cursors are operational. Any help is appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1401842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393744] Re: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04
modprobe -v rt61pci nohwcrypt=y did the job for me... seems to be quite stable now.. I'm still testing is the connection keeps running. -- 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/1393744 Title: 1814:0301 RT2x00/rt61pci disconnects since update to 15.04 Status in network-manager package in Ubuntu: Triaged Bug description: lsb_release -rd :Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 wi-fi disconnects and unable to reconnect since updates on 13-11-2014. Also affects Lubuntu 15.04 on same machine. Ubuntu 12.04.1 on same machine does not disconnect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.8.8-0ubuntu34 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 CurrentDesktop: XFCE Date: Tue Nov 18 11:12:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-01-14 (307 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140114) IpRoute: RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Petersbergd473a136-74dc-4695-aac3-1fffc9cc8095 802-11-wireless 1416308390 Tue 18 Nov 2014 10:59:50 GMT yes no /org/freedesktop/NetworkManager/Settings/2 BTWifi-with-FON a2b63b98-159a-49f4-9247-d46a0d67ed41 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 Petersberg 1 4fc01379-d340-479e-a016-9af1ab717c83 802-11-wireless 1416303120 Tue 18 Nov 2014 09:32:00 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8disconnectedenabled enabled enabledenabled disabled --- ApportVersion: 2.14.7-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: peter 1938 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=ffe4c76c-645c-4847-ba8c-b2323517a10f InstallationDate: Installed on 2014-01-14 (318 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140114) MachineType: VIA Technologies, Inc. VT8363 Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic root=UUID=ed3144cc-8873-40a1-9670-bb2bfc9190a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 RelatedPackageVersions: linux-restricted-modules-3.16.0-25-generic N/A linux-backports-modules-3.16.0-25-generic N/A linux-firmware 1.138 Tags: vivid Uname: Linux 3.16.0-25-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/01/2000 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 6.00 PG dmi.board.name: 8363-686A dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd08/01/2000:svnVIATechnologies,Inc.:pnVT8363:pvr:rvn:rn8363-686A:rvr:cvn:ct3:cvr: dmi.product.name: VT8363 dmi.sys.vendor: VIA Technologies, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1393744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452295] [NEW] package click-apparmor 0.2.11.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: My update to 15.04 was not successful. I'm prompted to run: apt-get install -f which does not succeed. (report is only for debugging; I'll do a clean install) ProblemType: Package DistroRelease: Ubuntu 15.04 Package: click-apparmor 0.2.11.2 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed May 6 10:13:23 2015 DuplicateSignature: package:click-apparmor:0.2.11.2:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-06-12 (693 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: click-apparmor Title: package click-apparmor 0.2.11.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-05-06 (0 days ago) ** Affects: click-apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1452295 Title: package click-apparmor 0.2.11.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in click-apparmor package in Ubuntu: New Bug description: My update to 15.04 was not successful. I'm prompted to run: apt-get install -f which does not succeed. (report is only for debugging; I'll do a clean install) ProblemType: Package DistroRelease: Ubuntu 15.04 Package: click-apparmor 0.2.11.2 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed May 6 10:13:23 2015 DuplicateSignature: package:click-apparmor:0.2.11.2:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-06-12 (693 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: click-apparmor Title: package click-apparmor 0.2.11.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1452295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452295] Re: package click-apparmor 0.2.11.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1452295 Title: package click-apparmor 0.2.11.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in click-apparmor package in Ubuntu: New Bug description: My update to 15.04 was not successful. I'm prompted to run: apt-get install -f which does not succeed. (report is only for debugging; I'll do a clean install) ProblemType: Package DistroRelease: Ubuntu 15.04 Package: click-apparmor 0.2.11.2 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed May 6 10:13:23 2015 DuplicateSignature: package:click-apparmor:0.2.11.2:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-06-12 (693 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: click-apparmor Title: package click-apparmor 0.2.11.2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to vivid on 2015-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1452295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059872] Re: Error formatting disk using disk utility
Any news on this bug for trusty? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1059872 Title: Error formatting disk using disk utility Status in udisks2 package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Status in udisks2 source package in Trusty: Invalid Status in util-linux source package in Trusty: Triaged Status in util-linux package in Debian: Fix Released Bug description: Formatting a SD card using the disk utility fails with an error message Error formatting disk - Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0) Steps to repro: Launch the disk utility Plug a SD card into the computer Select the SD card and click on the gears icon at the top right of the application From the drop down menu, select Format Disk maintain the default setting and select Format Acknowledge warnings After format process has been going for a while, the error message shown above pops up Workaround: After selecting the SD card, instead of clicking the gear icon to format, click the partition in the Volumes section. Delete the partition (minus icon) Create a new partition - The underlying problem is that the wipefs tool from util-linux does not work any more. === TEST CASE === $ sudo modprobe scsi_debug dev_size_mb=200 # this creates a new /dev/sdX, usually /dev/sdb; check dmesg! # now create a partition table $ cat EOF | sudo sfdisk /dev/sdb # partition table of /dev/sdb unit: sectors /dev/sdb1 : start= 32, size= 409568, Id=83 /dev/sdb2 : start=0, size=0, Id= 0 /dev/sdb3 : start=0, size=0, Id= 0 /dev/sdb4 : start=0, size=0, Id= 0 EOF # now create an ext4 file system: $ sudo mkfs.ext4 /dev/sdb1 # check contents: $ sudo blkid -p /dev/sdb /dev/sdb1 /dev/sdb: PTTYPE=dos /dev/sdb1: UUID=4bd1c542-a61f-43c4-a7e5-cc50e66e6b5a VERSION=1.0 TYPE=ext4 USAGE=filesystem PART_ENTRY_SCHEME=dos PART_ENTRY_TYPE=0x83 PART_ENTRY_NUMBER=1 PART_ENTRY_OFFSET=32 PART_ENTRY_SIZE=409568 PART_ENTRY_DISK=8:16 # wipe: $ sudo wipefs -a /dev/sdb # now check contents again $ sudo blkid -p /dev/sdb /dev/sdb1 # in the broken case, you will still see a dos partition table and the ext4 partition; in the working case, /dev/sdb won't show anything and /dev/sdb1 does not exist any more ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: udisks 1.0.4-6 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CustomUdevRuleFiles: 51-android.rules 51-android.rules~ Date: Mon Oct 1 15:07:46 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120720.1) MachineType: FOXCONN NT-A2400NT-A3500 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=fcc445e4-9662-47cc-855d-ca17ad1c2a87 ro quiet splash vt.handoff=7 SourcePackage: udisks UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd03/29/2011:svnFOXCONN:pnNT-A2400NT-A3500:pvrFAB1.0:rvnFOXCONN:rnNT-A2400NT-A3500:rvrFAB1.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400NT-A3500 dmi.product.version: FAB 1.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1059872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447756] Re: segfault in log.c code causes phone reboot loops
i dont think we should close this one, the bu still persists and need to urgently be fixed, the workaround we ship can not stay for log (since it removes all logging for system jobs) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: segfault in log.c code causes phone reboot loops Status in the base for Ubuntu mobile products: Fix Committed Status in Upstart: New Status in upstart package in Ubuntu: Confirmed Bug description: We recently started getting reprots from phone users that their devices go into a reboot loop after changing the language or getting an OTA upgrade (either of both end with a reboot of the phone) after a bit of research we collected the log at http://pastebin.ubuntu.com/10872934/ this shows a segfault of upstarts init binary in the log.c code: [6.999083]init: log.c:819: Assertion failed in log_clear_unflushed: log-unflushed-len [7.000279]init: Caught abort, core dumped [7.467176]Kernel panic - not syncing: Attempted to kill init! exitcode=0x0600 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1447756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432613] Re: Facebook and MSN messengers shutting down (third-party client access)
I think maybe I forgot or messed up somehow, let me look at that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1432613 Title: Facebook and MSN messengers shutting down (third-party client access) Status in Online Accounts: Account plugins: In Progress Status in Webapps Team Task Tracking Project: In Progress Status in account-plugins package in Ubuntu: Fix Committed Status in empathy package in Ubuntu: Fix Committed Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in account-plugins source package in Trusty: Fix Committed Status in empathy source package in Trusty: In Progress Status in ubuntu-system-settings-online-accounts source package in Trusty: Won't Fix Status in account-plugins source package in Utopic: Fix Committed Status in empathy source package in Utopic: Fix Committed Status in ubuntu-system-settings-online-accounts source package in Utopic: Won't Fix Status in account-plugins source package in Vivid: Fix Committed Status in empathy source package in Vivid: Fix Committed Status in ubuntu-system-settings-online-accounts source package in Vivid: Won't Fix Bug description: [ Description ] Facebook messenger and Windows Live messenger don't work any more because Facebook Microsoft removed third-party support for them. [ Fix QA ] Stop supporting IM accounts for these clients. For both creation continued use. Verify that if you add a WLM or FB account in online accounts, empathy doesn't try to connect to it. account-plugins-windows-live shouldn't be pulled in by default any more (check a trusty daily which is built with proposed). [ Regression potential ] This is a regression, in that we stop supporting some account types. We don't have a choice about this. [ Original description ] The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. I guess we need to correspondingly remove IM support for these services SRU it back. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1432613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452173] Re: [Dell Precision M4800] Regression: screen brightness control broken in 15.04
** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: nvidia-graphics-drivers-346-updates (Ubuntu) Status: New = Confirmed ** Changed in: nvidia-graphics-drivers-346-updates (Ubuntu) Importance: Undecided = High ** Changed in: xorg (Ubuntu) Status: New = Confirmed ** Changed in: xorg (Ubuntu) Importance: Undecided = High -- 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/1452173 Title: [Dell Precision M4800] Regression: screen brightness control broken in 15.04 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: In Ubuntu 15.04, I no longer am able to control the screen brightness. See possible similar bug #1411514 for 14.04.1. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Date: Wed May 6 10:12:03 2015 DistUpgraded: 2015-04-24 01:12:19,566 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05cc] InstallationDate: Installed on 2014-03-12 (419 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Precision M4800 PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed root=UUID=61c860cd-d55d-4e70-85a3-615b677b5811 ro nomodeset=1 splash quiet plymouth:debug=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-04-23 (12 days ago) dmi.bios.date: 12/03/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 5 22:22:48 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452300] [NEW] Reboot takes too long
Public bug reported: Test case. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: qa-regression ** Summary changed: - Reboots takes too long + Reboot takes too long -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in unity8 package in Ubuntu: New Bug description: Test case. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1452300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445512] Re: journalctl not showing all content in the log.
** Changed in: systemd (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1445512 Title: journalctl not showing all content in the log. Status in systemd package in Ubuntu: Confirmed Bug description: so the manual say this.. --- If called without parameters, it will show the full contents of the journal, starting with the oldest entry collected. --- This is not happening for me. if I do the following command journalctl | grep [program name] I get less output than if I do journalctl _COMM=[program name] My guess is that this is happening for the same reason that my previous bug where --list-boots did not work. Namely there seems to be a major problem when the log is corrupted and things behave inconsistently. journalctl --verify shows several corruptions but that should not make this type of inconsistent behavior. The systemd people have said repeatedly that there is no need for a repair tool and that systemd can handle corruptions just fine. Not my experience. Now the reason I get corruptions is probably due to unreliable suspend/resume where resume is not working an a power cycle is needed. This is not a uncommon thing suspend/resume just is not gong to be 100% and people are going to end up with journal that is corrupted. Note that the copy I get in syslog contain all the output I get when I run journalctl with the _COMM option. systemd journal handling needs to improve substantial so it can handle corruption better and at least be consistent with itself. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 17 15:59:13 2015 InstallationDate: Installed on 2015-04-09 (7 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) MachineType: Apple Inc. MacBookPro11,2 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-14-generic.efi.signed root=UUID=f84ca03e-c0d4-45ad-80f3-c45d4ad106dd ro rootflags=subvol=@ noprompt persistent quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP112.88Z.0138.B14.1501071031 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-3CBD00234E554E41 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-3CBD00234E554E41 dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B14.1501071031:bd01/07/2015:svnAppleInc.:pnMacBookPro11,2:pvr1.0:rvnAppleInc.:rnMac-3CBD00234E554E41:rvrMacBookPro11,2:cvnAppleInc.:ct10:cvrMac-3CBD00234E554E41: dmi.product.name: MacBookPro11,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1445512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled
** Package changed: indicator-datetime (Ubuntu) = unity-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1440157 Title: WARNING **: Could not connect to geoname lookup server: Operation was cancelled Status in One Hundred Papercuts: Confirmed Status in The Date and Time Indicator: New Status in unity-control-center package in Ubuntu: Confirmed Bug description: Test Case: open Date Time panel Clock Enable Time in other locations Click Choose Locations... No other locations can be added ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20150331-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CasperVersion: 1.358 CurrentDesktop: Unity Date: Fri Apr 3 23:54:13 2015 LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1440157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
On an old Intel Pentium 4 PC. This bug is one of the most annoying one I have ever encountered. ** Attachment added: Ginfo.txt https://bugs.launchpad.net/elementaryos/+bug/1390625/+attachment/4392231/+files/Ginfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 863358] Re: [pkg] Can't easily use Ubuntu without using Ubuntu Mono
As Ubuntu (proportional) and Ubuntu Mono have different family names it would probably make sense to split the binary packages produced into two .debs built at the same time—this would allow installing one or the other. Doing this as a one-off would be painful, but it would be relatively quick (5–10 minutes to actually change ./debian/{control,*.install} and then an hour or two testing upgrade testing combinations) to split these at the point of doing the next release. It makes sense to do this at the same time as bug #851457, as the rename to the New Debian Font Standard packaging names requires the same operations, and this would turn two rounds into a single round. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/863358 Title: [pkg] Can't easily use Ubuntu without using Ubuntu Mono Status in Ubuntu Font Family: New Status in ubuntu-font-family-sources package in Ubuntu: New Bug description: I find the Ubuntu font fairly attractive. On the other hand, I find the Ubuntu Mono font unpleasant and likely to slow down my work. I understand it is a matter of personal taste, but the reasons should be obvious from the attached image. On popular operating systems, it is easy to use one font but not another, even if they are related. I suggest that this be possible on Ubuntu with the Ubuntu fonts too. Probably the simplest way of implementing this would be to package them separately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/863358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1089010] Re: Keyboard shortcuts for lenses should be customizable in System Settings
** Tags added: unity -- 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/1089010 Title: Keyboard shortcuts for lenses should be customizable in System Settings Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: The keyboard shortcuts for opening the Unity dash to a specific lens should be customizable in System SettingsKeyboardShortcuts. This is useful for tweakers or for those who just want to see a list of what keyboard shortcuts are available (*discoverability*) [1]. Also, as we get more and more custom lenses, it's nearly unavoidable that multiple third-party lenses will try to use the same shortcut; the user should be able to manually fix that if desired. [1] Yes, there's the keyboard shortcut overlay but there won't be enough room for all shortcuts to be listed. Also, currently the overlay doesn't do high contrast so the System Settings view would be better for those who need high contrast. What we don't want is people needing to edit system files and have those changes lost whenever there are updates to that Unity lens. http://www.iloveubuntu.net/how-easily-add-preferred-keyboard- shortcuts-unity-lenses This can be done by adding the appropriate .xml to /usr/share/gnome- control-center/keybindings/ GNOME Shell puts their extra shortcuts (like 'Show the Message Tray') in the System category. And then the Unity lens specification would need to be updated so that developers use that method for keyboard shortcuts instead of the /usr/share/unity/lenses Shortcut= syntax. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily12.12.05-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-5.13-generic 3.7.0-rc8 Uname: Linux 3.7.0-5-generic x86_64 ApportVersion: 2.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Dec 11 11:16:32 2012 MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1089010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
Looks like this an issue related to boards with Intel integrated graphics. I may be wrong. Also on some occasions the corrupt mouse would get fixed by itself like on trying to take a screenshot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Confirmed Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 851084] Re: [pkg] does not show up in list returned by xfontsel, don't know 14-part font name
This likely needs a day or two of debugging depending. For fixing: once it's possible to rebuild the font, this is then likely to be relatively easy to patch; either in the source, or binary. And then an hour or so to confirm the fix works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-font-family-sources in Ubuntu. https://bugs.launchpad.net/bugs/851084 Title: [pkg] does not show up in list returned by xfontsel, don't know 14-part font name Status in Ubuntu Font Family: New Status in ubuntu-font-family-sources package in Ubuntu: New Bug description: Hi, Attempting to use xfontsel to find the 14-part font name (with the hopes of using this name to set this font as the default for Emacs), it appears that the font is not known to xfontsel. Similarly the font is not returned as an option by the Emacs `x-list-fonts' function. Is it possible that the apt-get instillation did not properly register the 14-part font name with the X server? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/851084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436252] Re: Behaves inconsistently when you unplug headphones
[5.170780] autoconfig: line_outs=1 (0x5/0x0/0x0/0x0/0x0) type:line [5.170784]speaker_outs=1 (0x7/0x0/0x0/0x0/0x0) [5.170786]hp_outs=1 (0x6/0x0/0x0/0x0/0x0) [5.170787]mono: mono_out=0x0 [5.170789]inputs: [5.170791] Mic=0x8 [5.170792] Line=0x9 control.21 { iface CARD name 'Line Out Jack' value true comment { access read type BOOLEAN count 1 } } control.22 { iface CARD name 'Front Headphone Jack' value true comment { access read type BOOLEAN count 1 } } control.23 { iface CARD name 'Speaker Phantom Jack' value true comment { access read type BOOLEAN count 1 } } seen bug in pulseaudio as line out is plugged , , line out is not selected when headphone is unplugged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436252 Title: Behaves inconsistently when you unplug headphones Status in PulseAudio sound server: New Status in pulseaudio package in Ubuntu: New Bug description: In the beginning headphones are plugged in, and Auto-Mute Mode set Disabled in alsamixer. Start pulseaudio. Then unplug headphones. Speakers are muted. Then plug headphones in. Speakers are muted. Then unplug headphones. Speaker volume is unmuted. I expect Speaker levels and muted/unmuted state of Speakers in alsamixer stay intact when you plug headphones in or out. And concerning the Auto-Mute Mode Disabled, Speakers should not get effectively muted when headphones are plugged in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-lowlatency 3.13.11-ckt16 Uname: Linux 3.13.0-48-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 2255 F panel-12-mixer jarnos 8103 F alsamixer jarnos 8313 F pulseaudio CurrentDesktop: XFCE Date: Wed Mar 25 11:59:07 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (185 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1436252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452300] Re: Reboot takes too long
I very much doubt this is an unity8 bug given that unity8 is not involved at these early stages. ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1452300 Title: Reboot takes too long Status in unity8 package in Ubuntu: Incomplete Bug description: Test case. - In the greeter screen, long press power button to display power dialog. - Tap to reboot. Expected result. - Must take similar time than stable. Actual result. - Stable takes 30 seconds to show the bq white screen. - 274 takes bewteen than 2 and 3 minutes to show the bq screen. syslog: May 6 14:16:35 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=816 x-info=http://w ww.rsyslog.com] exiting on signal 15. May 6 14:20:05 ubuntu-phablet rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=817 x-info=http://w ww.rsyslog.com] start current build number: 274 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1452300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1451232] Re: container does not receive IP address after 15.04 upgrade
And, so far, these steps are needed each time I reboot. 2 reboots after initial success. As you suggested, stopping and restarting the lxc-net systemd job is necessary. Just starting it does not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1451232 Title: container does not receive IP address after 15.04 upgrade Status in lxc package in Ubuntu: Incomplete Bug description: Perhaps this is an upgrade issue, perhaps it is a installation issue. In either case, there should be more information about upgrading lxc. After upgrading to Ubuntu 15.04, my container no longer started. After upgrading, I had to remove the following line from the config file for my container: lxc.network.link = lxcbr0 Here is the attempt at starting before commenting out the line: kevin@nereocystis:~$ sudo lxc-start -F -n escale_build lxc-start: conf.c: instantiate_veth: 2660 failed to attach 'vethTCPSQO' to the bridge 'lxcbr0': Operation not permitted lxc-start: conf.c: lxc_create_network: 2943 failed to create netdev lxc-start: start.c: lxc_spawn: 914 failed to create the network lxc-start: start.c: __lxc_start: 1164 failed to spawn 'escale_build' lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. After commenting out this line, the container starts, but no IP address is assigned in the container. But no IP address was assigned: For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/9a:9b:92:81:87:62 Sending on LPF/eth0/9a:9b:92:81:87:62 Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14 No DHCPOFFERS received. No working leases in persistent database - sleeping. done. Eventually, I purged lxc, and reinstalled it, with the same results. I also tried creating a new container from scratch using the instructions in: https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-network sudo lxc-create --template download --name u1 Again, no IP address. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 3 10:44:23 2015 InstallationDate: Installed on 2013-06-02 (699 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) KernLog: [56541.698842] audit: type=1400 audit(1430671655.848:49): apparmor=DENIED operation=mount info=failed flags match error=-13 profile=lxc-container-default name=/ pid=3109 comm=mount flags=ro, remount, relatime [56620.060697] audit: type=1400 audit(1430671734.154:50): apparmor=DENIED operation=mount info=failed type match error=-13 profile=lxc-container-default name=/sys/fs/cgroup/ pid=3403 comm=systemd flags=ro, nosuid, nodev, noexec, remount, strictatime SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1451232/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1445595] Re: Empty Trash Results in File Windows Opening
+1 -- 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/1445595 Title: Empty Trash Results in File Windows Opening Status in Unity: New Status in nautilus package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: When selecting 'empty trash' from the launcher I get a dialog to confirm the deletion and a file window. When emptying trash from nautilus window only get confirmation dialog as expected. Expected behavior: - Only confirm dialog pop up. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1445595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446809] Re: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Summary changed: - denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) + [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) Status in openldap package in Ubuntu: New Status in openldap package in Debian: Fix Released Bug description: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] TBD [Other Info] * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html * Patches backported: - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452238] Re: Failed to upgrade system from 14.04
Jonathan, Yes, it could resolve it. But it's not a better solution for it, it would be better that we find the root cause and fix it in ifupdown. :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1452238 Title: Failed to upgrade system from 14.04 Status in ifupdown: New Status in ifupdown package in Ubuntu: Confirmed Bug description: Download and install the 14.04 image. http://cdimage.ubuntu.com/ubuntu/releases/14.04/release/ubuntu-14.04-desktop-amd64+mac.iso $ sudo apt-get update $ sudo apt-get upgrade . Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for mime-support (3.54ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Setting up libdbus-1-3:amd64 (1.6.18-0ubuntu4.3) ... Setting up libcgmanager0:amd64 (0.24-0ubuntu7.3) ... Setting up libudev1:amd64 (204-5ubuntu20.11) ... Processing triggers for libc-bin (2.19-0ubuntu6.6) ... (Reading database ... 163205 files and directories currently installed.) Preparing to unpack .../ifupdown_0.7.47.2ubuntu4.1_amd64.deb ... Unpacking ifupdown (0.7.47.2ubuntu4.1) over (0.7.47.2ubuntu4) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... dpkg: dependency problems prevent configuration of ifupdown: ifupdown depends on initscripts (= 2.88dsf-25); however: Package initscripts is not configured yet. dpkg: error processing package ifupdown (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1452238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp