[Touch-packages] [Bug 1409696] Re: There is no 'headset' icon in the indicator bar when a headset is connected
Is this finally going to be implemented in a future or it is still on discussion? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1409696 Title: There is no 'headset' icon in the indicator bar when a headset is connected Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Incomplete Bug description: Reported by an OEM who's phone currently does have such an icon, there is no visual indication that a wired headset has been connected to the phone and in use: [Procedures] 1.insert the earphone [Expect results] should be has earphone icon and notification shows in Status Bar [Actual results] There is no earphone icon in indicator Bar when inserting the earphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1409696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416141] Re: Sync jasper 1.900.1-debian1-2.4 (main) from Debian unstable (main)
This bug was fixed in the package jasper - 1.900.1-debian1-2.4 Sponsored for Artur Rona (ari-tczew) --- jasper (1.900.1-debian1-2.4) unstable; urgency=high * Non-maintainer upload. * Add 07-CVE-2014-8157.patch patch. CVE-2014-8157: dec->numtiles off-by-one check in jpc_dec_process_sot(). (Closes: #775970) * Add 08-CVE-2014-8158.patch patch. CVE-2014-8158: unrestricted stack memory use in jpc_qmfb.c (Closes: #775970) -- Salvatore Bonaccorso Thu, 22 Jan 2015 17:09:24 +0100 ** Changed in: jasper (Ubuntu) Status: New => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-8157 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-8158 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jasper in Ubuntu. https://bugs.launchpad.net/bugs/1416141 Title: Sync jasper 1.900.1-debian1-2.4 (main) from Debian unstable (main) Status in jasper package in Ubuntu: Fix Released Bug description: Please sync jasper 1.900.1-debian1-2.4 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * SECURITY UPDATE: denial of service or code execution via off-by-one - debian/patches/07-CVE-2014-8157.patch: fix off-by-one in src/libjasper/jpc/jpc_dec.c. - CVE-2014-8157 * SECURITY UPDATE: denial of service or code execution via memory corruption - debian/patches/08-CVE-2014-8158.patch: remove HAVE_VLA to use more sensible buffer sizes in src/libjasper/jpc/jpc_qmfb.c. - CVE-2014-8158 Debian fixed CVEs, as well. Changelog entries since current vivid version 1.900.1-debian1-2.3ubuntu1: jasper (1.900.1-debian1-2.4) unstable; urgency=high * Non-maintainer upload. * Add 07-CVE-2014-8157.patch patch. CVE-2014-8157: dec->numtiles off-by-one check in jpc_dec_process_sot(). (Closes: #775970) * Add 08-CVE-2014-8158.patch patch. CVE-2014-8158: unrestricted stack memory use in jpc_qmfb.c (Closes: #775970) -- Salvatore Bonaccorso Thu, 22 Jan 2015 17:09:24 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jasper/+bug/1416141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416293] [NEW] android container should not enable adb and mtp from default.prop
Public bug reported: if the android container rootfs is built with ro.debuggable=1 it will put a default.prop file into the container rootfs with persist.sys.usb.config set to mtp,adb. on first boot after a factory flach (not usin ubuntu-device-flash) when there was no value for this property set prior to starting the container this causes the gadget to be in adb mode without running adbd daemon. in his case the device will show up as "offline" in "adb devices" on a PC until developer mode was toggled once in the settings UI. lxc-android-config needs to ship a pre-start.d snippet that removes this entry from default.prop. this way recovery boots can still benefit from ro.debuggable being set while adb behavior will not be affected in normal boots. --- /var/lib/lxc/android/pre-start.d/20-no-default-prop-adb --- #! /bin/sh sed -i '/^persist.sys.usb.config=.*/d' $LXC_ROOTFS_PATH/default.prop --- ** Affects: lxc-android-config (Ubuntu) Importance: High Assignee: Oliver Grawert (ogra) Status: In Progress ** Affects: lxc-android-config (Ubuntu RTM) Importance: High Assignee: Oliver Grawert (ogra) Status: In Progress ** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) => Oliver Grawert (ogra) ** Changed in: lxc-android-config (Ubuntu) Status: New => In Progress ** Changed in: lxc-android-config (Ubuntu) Importance: Undecided => High ** Also affects: lxc-android-config (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: lxc-android-config (Ubuntu RTM) Status: New => In Progress ** Changed in: lxc-android-config (Ubuntu RTM) Importance: Undecided => High ** Changed in: lxc-android-config (Ubuntu RTM) Assignee: (unassigned) => Oliver Grawert (ogra) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1416293 Title: android container should not enable adb and mtp from default.prop Status in lxc-android-config package in Ubuntu: In Progress Status in lxc-android-config package in Ubuntu RTM: In Progress Bug description: if the android container rootfs is built with ro.debuggable=1 it will put a default.prop file into the container rootfs with persist.sys.usb.config set to mtp,adb. on first boot after a factory flach (not usin ubuntu-device-flash) when there was no value for this property set prior to starting the container this causes the gadget to be in adb mode without running adbd daemon. in his case the device will show up as "offline" in "adb devices" on a PC until developer mode was toggled once in the settings UI. lxc-android-config needs to ship a pre-start.d snippet that removes this entry from default.prop. this way recovery boots can still benefit from ro.debuggable being set while adb behavior will not be affected in normal boots. --- /var/lib/lxc/android/pre-start.d/20-no-default-prop-adb --- #! /bin/sh sed -i '/^persist.sys.usb.config=.*/d' $LXC_ROOTFS_PATH/default.prop --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1416293/+subscriptions -- Mailing list: https://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 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
On 29.1.2015 14:30, Bruno Nova wrote: > ** Tags removed: verification-done > ** Tags added: verification-needed > GUI for kbd is screwed up since ubuntu 12 workaround is command ( eg for alt gr international): setxkbmap -rules evdev -model evdev -layout us -variant altgr-intl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in indicator-keyboard package in Ubuntu: Won't Fix Status in ibus source package in Trusty: Fix Committed Status in indicator-keyboard source package in Trusty: Won't Fix Bug description: [Impact] When first boot into Unity desktop, English keyboard layout is active while all other parts of the system language settings are set to another language (e.g. German). The bug is properly addressed in newer upstream releases in Vivid, but the changes is too intrusive and not suitable for being back ported in SRU. And changing the default to use system keyboard layout solves the problem. [Test Case] 1. Set the system language to something other than English, e.g. German. 2. Create a new user, log in to the Unity desktop of the new user. 3. Check the keyboard layout, it should be German instead of English. [Regression Potential] Since this changes the default value of the keyboard layout settings by using system defined as default, it avoids using ibus's built-in keyboard layout related functionality, so that this could be a regression for users rely on this certain behavior (e.g. use English keyboard while want to keep the system language settings to German), but such behavior is not expected for normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416293] Re: android container should not enable adb and mtp from default.prop
** Description changed: if the android container rootfs is built with ro.debuggable=1 it will put a default.prop file into the container rootfs with persist.sys.usb.config set to mtp,adb. on first boot after a factory - flach (not usin ubuntu-device-flash) when there was no value for this + flash (not using ubuntu-device-flash) when there was no value for this property set prior to starting the container this causes the gadget to be in adb mode without running adbd daemon. in his case the device will show up as "offline" in "adb devices" on a PC until developer mode was toggled once in the settings UI. lxc-android-config needs to ship a pre-start.d snippet that removes this entry from default.prop. this way recovery boots can still benefit from ro.debuggable being set while adb behavior will not be affected in normal boots. --- /var/lib/lxc/android/pre-start.d/20-no-default-prop-adb --- #! /bin/sh sed -i '/^persist.sys.usb.config=.*/d' $LXC_ROOTFS_PATH/default.prop --- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1416293 Title: android container should not enable adb and mtp from default.prop Status in lxc-android-config package in Ubuntu: In Progress Status in lxc-android-config package in Ubuntu RTM: In Progress Bug description: if the android container rootfs is built with ro.debuggable=1 it will put a default.prop file into the container rootfs with persist.sys.usb.config set to mtp,adb. on first boot after a factory flash (not using ubuntu-device-flash) when there was no value for this property set prior to starting the container this causes the gadget to be in adb mode without running adbd daemon. in his case the device will show up as "offline" in "adb devices" on a PC until developer mode was toggled once in the settings UI. lxc-android-config needs to ship a pre-start.d snippet that removes this entry from default.prop. this way recovery boots can still benefit from ro.debuggable being set while adb behavior will not be affected in normal boots. --- /var/lib/lxc/android/pre-start.d/20-no-default-prop-adb --- #! /bin/sh sed -i '/^persist.sys.usb.config=.*/d' $LXC_ROOTFS_PATH/default.prop --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1416293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411100] Re: Guest user not removed after guest session ends when using bash as default shell
Doesn't seem there is something left to sponsor (fixes is in current serie and stable one, likely going to be part of the next SRU), unsubscribing sponsors -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1411100 Title: Guest user not removed after guest session ends when using bash as default shell Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Triaged Status in lightdm source package in Trusty: Fix Committed Status in lightdm source package in Utopic: Fix Committed Bug description: The /usr/sbin/giest-account script contains a bug which prevents the removal of guest accounts: $ sudo /usr/sbin/guest-account remove guest-Hhiook /usr/sbin/guest-account: line 129: UID: readonly variable Maybe this is related to /bin/sh actually beeing a Bash: $ ll -d /bin/sh lrwxrwxrwx 1 root root 4 Jan 1 01:44 /bin/sh -> bash* But since using Bash as default sh is still a "feature" of Ubuntu, all scripts should work with both. Running the script with dash actually works: $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva umount: /tmp/guest-ZWCtva: mountpoint not found umount: /tmp/guest-ZWCtva: mountpoint not found Removing user `guest-ZWCtva' ... Warning: group `guest-ZWCtva' has no more members. Done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1411100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416293] Re: android container should not enable adb and mtp from default.prop
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1416293 Title: android container should not enable adb and mtp from default.prop Status in the base for Ubuntu mobile products: New Status in lxc-android-config package in Ubuntu: In Progress Status in lxc-android-config package in Ubuntu RTM: In Progress Bug description: if the android container rootfs is built with ro.debuggable=1 it will put a default.prop file into the container rootfs with persist.sys.usb.config set to mtp,adb. on first boot after a factory flash (not using ubuntu-device-flash) when there was no value for this property set prior to starting the container this causes the gadget to be in adb mode without running adbd daemon. in his case the device will show up as "offline" in "adb devices" on a PC until developer mode was toggled once in the settings UI. lxc-android-config needs to ship a pre-start.d snippet that removes this entry from default.prop. this way recovery boots can still benefit from ro.debuggable being set while adb behavior will not be affected in normal boots. --- /var/lib/lxc/android/pre-start.d/20-no-default-prop-adb --- #! /bin/sh sed -i '/^persist.sys.usb.config=.*/d' $LXC_ROOTFS_PATH/default.prop --- To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all
The following headsets were tested on Lenovo ThinkPad X240 (CID 201307-14019) and could reproduce this bug. They are[1]: OMTP: Nokia WH-102 HS125 CTIA: SONY MH-EX300AP, Samsung (unknown model), HTC (unknown model) [1] It is hard to know which type the headset is because there is no model label, and even there is a model label, the data searched from internet seems to be unclear or very few. I confirmed the type by the brands because of history background of the development of the pole standard, and a electronic multimeter to measure the resistance of the poles of the headsets. -- 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/1414706 Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all Status in HWE Next Project: Incomplete Status in alsa-driver package in Ubuntu: Confirmed Bug description: During this test, an error dialog was thrown, reading: The following mixer control(s) might be incorrectly set: Mic is at 0.0% Mic is muted Please try to fix that (e g by running "alsamixer -D hw:PCH" in a terminal) and see if that solves the problem. Would you like to continue troubleshooting anyway? However, the System Settings... -> Sound UI shows the mic as not muted. When I tried running the alsamixer command, I saw mic and mic- boost were both showing 0; I cranked them up to 100, but it made no difference. I also tried re-running this command with the mic/mic- boost still set to 100 and it threw the same error. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 26 16:20:49 2015 InstallationDate: Installed on 2014-09-10 (138 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 1 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET75WW (2.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ALCTO1WW dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 921839] Re: gdb reports ImportError no module libstdcxx.v6.printers
Hello guys! I met the similar problem . When run gdb ,it shows like that: Traceback (most recent call last): File "",line 3, in File "/root/.gdb/python/libstdcxx/v6/_init_.py",line 19,in from printers import register_libstdcxx_printers ImportError: No module named 'printers' /root/.gdbinit:4007:Error in sourced command file: Error while executing Python code. And I just update with the repository ppa:ubuntu-toolchain-r/test as what you said, It still didn't work. Any suggestions ? Thank you all -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/921839 Title: gdb reports ImportError no module libstdcxx.v6.printers Status in gdb package in Ubuntu: Invalid Bug description: GDB attempts to use a python "pretty printer" and reports the following error: [Thread debugging using libthread_db enabled] Traceback (most recent call last): File "/usr/local/lib64/libstdc++.so.6.0.16-gdb.py", line 59, in from libstdcxx.v6.printers import register_libstdcxx_printers ImportError: No module named libstdcxx.v6.printers [Inferior 1 (process 31059) exited normally] (gdb) GDB Version: GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08 I found that by doing the following it fixes the problem: svn co svn://gcc.gnu.org/svn/gcc/trunk/libstdc++-v3/python gdb_printers mv gdb_printers /usr/local/etc cd ~ vi .gdbinit (copy & paste into .gdbinit) python import sys sys.path.insert(0, '/usr/local/etc/gdb_printers') from libstdcxx.v6.printers import register_libstdcxx_printers register_libstdcxx_printers (None) end To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/921839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415871] Re: screen lock suddenly appear
maybe it is the same bug? https://bugs.launchpad.net/unity-greeter/+bug/1393843 -- 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/1415871 Title: screen lock suddenly appear Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Lock screen suddenly appears, sometimes. In the middle I use browser or another program. It always happens when I lock the screen, and then releases the lock. It never happens when I start the computer for the first time. $ lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 $ apt-cache policy unity unity: Installed: 7.3.1+14.10.20141016-0ubuntu1 Candidate: 7.3.1+14.10.20141016-0ubuntu1 Version table: *** 7.3.1+14.10.20141016-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .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: Thu Jan 29 13:51:00 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-25-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-28-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-29-generic, x86_64: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff00] InstallationDate: Installed on 2014-12-08 (51 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: TOSHIBA Satellite L500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=d0060b13-5821-4f09-9346-d66290da86d2 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/10 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.90 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 9 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr1.90:bd09/08/10:svnTOSHIBA:pnSatelliteL500:pvrPSLS6E-00M00NH2:rvnTOSHIBA:rnNSWAA:rvr1.00:cvnTOSHIBA:ct9:cvrN/A: dmi.product.name: Satellite L500 dmi.product.version: PSLS6E-00M00NH2 dmi.sys.vendor: TOSHIBA 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.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: Wed Jan 28 23:36:57 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21825 vendor SEC xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1415871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409696] Re: There is no 'headset' icon in the indicator bar when a headset is connected
@Noemi - the status indicates it is still under discussion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1409696 Title: There is no 'headset' icon in the indicator bar when a headset is connected Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Incomplete Bug description: Reported by an OEM who's phone currently does have such an icon, there is no visual indication that a wired headset has been connected to the phone and in use: [Procedures] 1.insert the earphone [Expect results] should be has earphone icon and notification shows in Status Bar [Actual results] There is no earphone icon in indicator Bar when inserting the earphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1409696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416293] Re: android container should not enable adb and mtp from default.prop
This bug was fixed in the package lxc-android-config - 0.217 --- lxc-android-config (0.217) vivid; urgency=medium * make sure persist.sys.usb.config is not set in default.prop on builds with ro.debuggable=1 enabled (LP: #1416293) -- Oliver GrawertFri, 30 Jan 2015 09:31:22 +0100 ** Changed in: lxc-android-config (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1416293 Title: android container should not enable adb and mtp from default.prop Status in the base for Ubuntu mobile products: New Status in lxc-android-config package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu RTM: In Progress Bug description: if the android container rootfs is built with ro.debuggable=1 it will put a default.prop file into the container rootfs with persist.sys.usb.config set to mtp,adb. on first boot after a factory flash (not using ubuntu-device-flash) when there was no value for this property set prior to starting the container this causes the gadget to be in adb mode without running adbd daemon. in his case the device will show up as "offline" in "adb devices" on a PC until developer mode was toggled once in the settings UI. lxc-android-config needs to ship a pre-start.d snippet that removes this entry from default.prop. this way recovery boots can still benefit from ro.debuggable being set while adb behavior will not be affected in normal boots. --- /var/lib/lxc/android/pre-start.d/20-no-default-prop-adb --- #! /bin/sh sed -i '/^persist.sys.usb.config=.*/d' $LXC_ROOTFS_PATH/default.prop --- To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416328] [NEW] Does not reply on dbus when busy (e.g. downloading)
Public bug reported: We ran into the issue that system-image-dbus would sometimes not reply on snappy. After long debugging and deep dive into the go-dbus code it seems that system-image-dbus simply does not reply when its busy, at least in the snappy branch. This may well be fixed in the 3.0 branch so here is a test and it would be great to know if that works with the curl backend and the 3.0 branch: Ensure there is something for s-i-dbus to do (e.g. download new image): $ rm -f /writable/cache/*.tar.xz $ dbus-send --system --dest=com.canonical.SystemImage --type=method_call --print-reply /Service com.canonical.SystemImage.CheckForUpdate && sleep 1 && dbus-send --system --dest=com.canonical.SystemImage --type=method_call --print-reply /Service com.canonical.SystemImage.DownloadUpdate && sleep 1 && dbus-send --system --dest=com.canonical.SystemImage --type=method_call --reply- timeout=5000 --print-reply /Service com.canonical.SystemImage.Information Running the above gives me: """ method return sender=:1.54 -> dest=:1.53 reply_serial=2 method return sender=:1.54 -> dest=:1.55 reply_serial=2 Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. """ So it appears the curl backend is not quite there for snappy yet. ** Affects: system-image (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1416328 Title: Does not reply on dbus when busy (e.g. downloading) Status in system-image package in Ubuntu: New Bug description: We ran into the issue that system-image-dbus would sometimes not reply on snappy. After long debugging and deep dive into the go-dbus code it seems that system-image-dbus simply does not reply when its busy, at least in the snappy branch. This may well be fixed in the 3.0 branch so here is a test and it would be great to know if that works with the curl backend and the 3.0 branch: Ensure there is something for s-i-dbus to do (e.g. download new image): $ rm -f /writable/cache/*.tar.xz $ dbus-send --system --dest=com.canonical.SystemImage --type=method_call --print-reply /Service com.canonical.SystemImage.CheckForUpdate && sleep 1 && dbus-send --system --dest=com.canonical.SystemImage --type=method_call --print- reply /Service com.canonical.SystemImage.DownloadUpdate && sleep 1 && dbus-send --system --dest=com.canonical.SystemImage --type=method_call --reply-timeout=5000 --print-reply /Service com.canonical.SystemImage.Information Running the above gives me: """ method return sender=:1.54 -> dest=:1.53 reply_serial=2 method return sender=:1.54 -> dest=:1.55 reply_serial=2 Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. """ So it appears the curl backend is not quite there for snappy yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1416328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416349] [NEW] package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: sub-processo script post-removal instalado retornou estado de saída de erro 1
Public bug reported: This began after I installed xubuntu-desktop package and tried to reconfigure lightdm and unity-greeter. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: ubuntu-desktop: Purge lightdm: Purge Architecture: amd64 Date: Wed Jan 28 16:09:01 2015 DuplicateSignature: package:lightdm:1.10.3-0ubuntu2:sub-processo script post-removal instalado retornou estado de saída de erro 1 ErrorMessage: sub-processo script post-removal instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2014-11-25 (65 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmConfig: [Defaults] greeter-session=unity-greeter SourcePackage: lightdm Title: package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: sub-processo script post-removal instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1416349 Title: package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: sub- processo script post-removal instalado retornou estado de saída de erro 1 Status in lightdm package in Ubuntu: New Bug description: This began after I installed xubuntu-desktop package and tried to reconfigure lightdm and unity-greeter. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: ubuntu-desktop: Purge lightdm: Purge Architecture: amd64 Date: Wed Jan 28 16:09:01 2015 DuplicateSignature: package:lightdm:1.10.3-0ubuntu2:sub-processo script post-removal instalado retornou estado de saída de erro 1 ErrorMessage: sub-processo script post-removal instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2014-11-25 (65 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmConfig: [Defaults] greeter-session=unity-greeter SourcePackage: lightdm Title: package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: sub-processo script post-removal instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1416349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all
tested on: Lenovo ThinkPad X240 (CID 201307-14019) 3.13.0-44-generic #73 and package ii oem-audio-hda-daily-dkms 0.201501291151~ubuntu all HDA driver in DKMS format. could reproduce this bug. -- 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/1414706 Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all Status in HWE Next Project: Incomplete Status in alsa-driver package in Ubuntu: Confirmed Bug description: During this test, an error dialog was thrown, reading: The following mixer control(s) might be incorrectly set: Mic is at 0.0% Mic is muted Please try to fix that (e g by running "alsamixer -D hw:PCH" in a terminal) and see if that solves the problem. Would you like to continue troubleshooting anyway? However, the System Settings... -> Sound UI shows the mic as not muted. When I tried running the alsamixer command, I saw mic and mic- boost were both showing 0; I cranked them up to 100, but it made no difference. I also tried re-running this command with the mic/mic- boost still set to 100 and it threw the same error. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 26 16:20:49 2015 InstallationDate: Installed on 2014-09-10 (138 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 1 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET75WW (2.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ALCTO1WW dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416349] Re: package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: sub-processo script post-removal instalado retornou estado de saída de erro 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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1416349 Title: package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: sub- processo script post-removal instalado retornou estado de saída de erro 1 Status in lightdm package in Ubuntu: New Bug description: This began after I installed xubuntu-desktop package and tried to reconfigure lightdm and unity-greeter. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: ubuntu-desktop: Purge lightdm: Purge Architecture: amd64 Date: Wed Jan 28 16:09:01 2015 DuplicateSignature: package:lightdm:1.10.3-0ubuntu2:sub-processo script post-removal instalado retornou estado de saída de erro 1 ErrorMessage: sub-processo script post-removal instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2014-11-25 (65 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmConfig: [Defaults] greeter-session=unity-greeter SourcePackage: lightdm Title: package lightdm 1.10.3-0ubuntu2 failed to install/upgrade: sub-processo script post-removal instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1416349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375756] Re: Weather scope is not detecting the correct location
** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (stolowski) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1375756 Title: Weather scope is not detecting the correct location Status in the base for Ubuntu mobile products: Confirmed Status in unity-scopes-shell package in Ubuntu: New Bug description: It seems its using geoip so the automatically detected location is usually not correct, In my case its showing weather for a small city 90 miles away, Refreshing does not resolve it. The maps apps detect exact location. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1375756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415481] Re: default mmap_min_addr for arm64 prevents running arm32 applications
Newer versions of binutils should start ARM binaries at a higher start address to address this issue in a general way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1415481 Title: default mmap_min_addr for arm64 prevents running arm32 applications Status in procps package in Ubuntu: Fix Released Status in procps source package in Trusty: Fix Committed Status in procps source package in Utopic: Fix Committed Bug description: [ SRU Justification ] Executing 32-bit arm binaries as user fails on arm64. Turns out, this is bad. [ Test Case ] Grab a 32-bit binary (either multiarch via armhf, or compile a quick static hello) and try to run it. Also, check /proc/sys/vm/mmap_min_addr is set to 32k instead of 64k after boot. [ Regression Potential ] Shouldn't be any issue with 4k pagesize kernels, and this was already the default on 32-bit ARM for the same reasons. It could, potentially, mean that the zero page is no longer entirely protected from mmap when running a 64k pagesize kernel, however we don't currently ship such a kernel, preferring instead to have 32-bit compatibility. [ Original Bug Report ] Executing 32-bit arm binaries as user fails on arm64: # file hello hello: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, for GNU/Linux 2.6.32, BuildID[sha1]=c37a3b366d645eee600963a535370fa0bad9b2c0, not stripped # ./hello hello world # su - linaro $ /root/hello Segmentation fault Root cause was identified to /etc/sysctl.d/10-zeropage.conf, which is set on arm64 to 65536. To run legacy binaries, this should be set to 32768 like on armhf anr armel. Reference discussion: http://lists.infradead.org/pipermail/linux-arm- kernel/2015-January/320454.html Affects trusty, utopic and vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1415481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375756] Re: Weather scope is not detecting the correct location
** Branch linked: lp:~unity-api-team/unity-scopes-api/smart-scopes-lat- lon-rtm ** Also affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-scopes-api (Ubuntu RTM) Importance: Undecided Status: New ** No longer affects: unity-scopes-api (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1375756 Title: Weather scope is not detecting the correct location Status in the base for Ubuntu mobile products: Confirmed Status in unity-scopes-shell package in Ubuntu: New Status in unity-scopes-api package in Ubuntu RTM: New Bug description: It seems its using geoip so the automatically detected location is usually not correct, In my case its showing weather for a small city 90 miles away, Refreshing does not resolve it. The maps apps detect exact location. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1375756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1244127] 1% podatku - dla Mai i Michała
Witam, w najbliższym czasie Wszyscy musimy rozliczyć się z US za rok 2014. Przy okazji tej możemy odliczyć 1% podatku na różnego rodzaju instytucje pożytku publicznego. Bliźniaki Maja i Michał są zrzeszone w Polskim Towarzystwie Walki z Mukowiscydozą. Jeśli jeszcze nie przekazujecie nikomu 1% swojego podatku, a chcecie to zrobić, przekażcie go proszę na leczenie Majki i Michała. W załączniku znajdują się materiały które ułatwią Wam wpisanie w PIT niezbędnych informacji. Zachęcam też do odwiedzenia strony www.apel-majaimichal.pl z której możecie więcej dowiedzieć się na temat choroby dzieci. Jednocześnie chciałbym serdecznie podziękować wszystkim osobom które odliczyły swój jeden procent na moje dzieciaki w roku ubiegłym. Dziękuję. *Pozdrawiam,* *Dariusz Sawicki* ** Attachment added: "Karta_1_2015.jpg" https://bugs.launchpad.net/bugs/1244127/+attachment/4308796/+files/Karta_1_2015.jpg ** Attachment added: "Plakat 1% 2015 v.2.pdf" https://bugs.launchpad.net/bugs/1244127/+attachment/4308797/+files/Plakat%201%25%202015%20v.2.pdf -- 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/1244127 Title: [W55xEU, VIA VT1802, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I dont hear sound ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darek 2167 F pulseaudio /dev/snd/pcmC0D0c: darek 2167 F...m pulseaudio Date: Thu Oct 24 11:04:58 2013 InstallationDate: Installed on 2013-10-22 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: darek 2167 F pulseaudio /dev/snd/pcmC0D0c: darek 2167 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [W55xEU, VIA VT1802, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W55xEU dmi.board.vendor: CLEVO CO. dmi.board.version: D02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/05/2013:svnCLEVOCO.:pnW55xEU:pvrNotApplicable:rvnCLEVOCO.:rnW55xEU:rvrD02:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W55xEU dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1244127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388235] Re: [indicators] Battery icon turns red at 30%
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1388235 Title: [indicators] Battery icon turns red at 30% Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Triaged Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415481] Re: default mmap_min_addr for arm64 prevents running arm32 applications
Hi Brian, I've installed the procps package on trusty arm64 machine, rebooted and verified the correct value is set in /proc/sys/vm/mmap_min_addr. I haven't tested on utopic but see no reason why it wouldn't work there as well. Riku -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1415481 Title: default mmap_min_addr for arm64 prevents running arm32 applications Status in procps package in Ubuntu: Fix Released Status in procps source package in Trusty: Fix Committed Status in procps source package in Utopic: Fix Committed Bug description: [ SRU Justification ] Executing 32-bit arm binaries as user fails on arm64. Turns out, this is bad. [ Test Case ] Grab a 32-bit binary (either multiarch via armhf, or compile a quick static hello) and try to run it. Also, check /proc/sys/vm/mmap_min_addr is set to 32k instead of 64k after boot. [ Regression Potential ] Shouldn't be any issue with 4k pagesize kernels, and this was already the default on 32-bit ARM for the same reasons. It could, potentially, mean that the zero page is no longer entirely protected from mmap when running a 64k pagesize kernel, however we don't currently ship such a kernel, preferring instead to have 32-bit compatibility. [ Original Bug Report ] Executing 32-bit arm binaries as user fails on arm64: # file hello hello: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, for GNU/Linux 2.6.32, BuildID[sha1]=c37a3b366d645eee600963a535370fa0bad9b2c0, not stripped # ./hello hello world # su - linaro $ /root/hello Segmentation fault Root cause was identified to /etc/sysctl.d/10-zeropage.conf, which is set on arm64 to 65536. To run legacy binaries, this should be set to 32768 like on armhf anr armel. Reference discussion: http://lists.infradead.org/pipermail/linux-arm- kernel/2015-January/320454.html Affects trusty, utopic and vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1415481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all
** Changed in: hwe-next Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1414706 Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all Status in HWE Next Project: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: During this test, an error dialog was thrown, reading: The following mixer control(s) might be incorrectly set: Mic is at 0.0% Mic is muted Please try to fix that (e g by running "alsamixer -D hw:PCH" in a terminal) and see if that solves the problem. Would you like to continue troubleshooting anyway? However, the System Settings... -> Sound UI shows the mic as not muted. When I tried running the alsamixer command, I saw mic and mic- boost were both showing 0; I cranked them up to 100, but it made no difference. I also tried re-running this command with the mic/mic- boost still set to 100 and it threw the same error. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 26 16:20:49 2015 InstallationDate: Installed on 2014-09-10 (138 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 1 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET75WW (2.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ALCTO1WW dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416037] Re: [osk] Language button should always be visible
** Summary changed: - Language button should always be visible + [osk] Language button should always be visible -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1416037 Title: [osk] Language button should always be visible Status in the base for Ubuntu mobile products: New Status in Ubuntu Keyboard: New Status in Ubuntu UX bugs: New Status in ubuntu-keyboard package in Ubuntu: New Status in ubuntu-keyboard package in Ubuntu RTM: New Bug description: Currently the language button is only displayed if the user has more than one layout enabled. To make settings more discoverable this should be enabled all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400730] Re: libxext fills up .xsession-errors log files
** Bug watch removed: freedesktop.org Bugzilla #85064 https://bugs.freedesktop.org/show_bug.cgi?id=85064 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxext in Ubuntu. https://bugs.launchpad.net/bugs/1400730 Title: libxext fills up .xsession-errors log files Status in libxext package in Ubuntu: Fix Released Status in libxext source package in Utopic: Fix Committed Status in libxext source package in Vivid: Fix Released Bug description: libxext can write debug output, and it can write so much of it that it fills up .xsession-errors t be several GB and fill up the hard disk (or the equivalent file with lightdm). error is "_xgeWireToEvent: Unknown extension 148, this should never happen" [TEST CASE] Install Plasma 5 on utopic Use it for a while Notice that ~/.xsession-errors is filling up saying "_xgeWireToEvent: Unknown extension 148, this should never happen" with the new packages this will not happen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxext/+bug/1400730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373221] Re: guvcview crashed with SIGSEGV in get_ctrl_by_id()
> Ok. I'll wait for your results. Without sound, the same problem occurs... >> Should i open a new bug? > Yes please, this is a different bug. Here it is: https://bugs.launchpad.net/ubuntu/+source/guvcview/+bug/1416398 Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1373221 Title: guvcview crashed with SIGSEGV in get_ctrl_by_id() Status in GTK uvc viewer: Confirmed Status in One Hundred Papercuts: Triaged Status in libv4l v4l-utils: Confirmed Status in guvcview package in Ubuntu: Triaged Status in v4l-utils package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Launch guvcview EXPECTED BEHAVIOUR: - The application to start normally. REAL BEHAVIOUR: - The application crashes. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: guvcview 1.7.3-1.1build2 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 24 06:35:20 2014 ExecutablePath: /usr/bin/guvcview InstallationDate: Installed on 2013-05-21 (490 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcCmdline: guvcview SegvAnalysis: Segfault happened at: 0x42d970: mov0x0,%eax PC (0x0042d970) ok source "0x0" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: guvcview StacktraceTop: ?? () ?? () ?? () ?? () __libc_start_main (main=0x409920, argc=1, argv=0x7fff32c34208, init=, fini=, rtld_fini=, stack_end=0x7fff32c341f8) at libc-start.c:287 Title: guvcview crashed with SIGSEGV in __libc_start_main() UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1373221/+subscriptions -- Mailing list: https://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 1373221] Re: guvcview crashed with SIGSEGV in get_ctrl_by_id()
On Jan 28, 2015 at 11:17, Paulo Assis wrote: > Ok. I'll wait for your results. Without sound, the same problem occurs... >> Should i open a new bug? > Yes please, this is a different bug. Here it is: https://bugs.launchpad.net/ubuntu/+source/guvcview/+bug/1416398 Thank you. // -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1373221 Title: guvcview crashed with SIGSEGV in get_ctrl_by_id() Status in GTK uvc viewer: Confirmed Status in One Hundred Papercuts: Triaged Status in libv4l v4l-utils: Confirmed Status in guvcview package in Ubuntu: Triaged Status in v4l-utils package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Launch guvcview EXPECTED BEHAVIOUR: - The application to start normally. REAL BEHAVIOUR: - The application crashes. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: guvcview 1.7.3-1.1build2 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 24 06:35:20 2014 ExecutablePath: /usr/bin/guvcview InstallationDate: Installed on 2013-05-21 (490 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcCmdline: guvcview SegvAnalysis: Segfault happened at: 0x42d970: mov0x0,%eax PC (0x0042d970) ok source "0x0" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: guvcview StacktraceTop: ?? () ?? () ?? () ?? () __libc_start_main (main=0x409920, argc=1, argv=0x7fff32c34208, init=, fini=, rtld_fini=, stack_end=0x7fff32c341f8) at libc-start.c:287 Title: guvcview crashed with SIGSEGV in __libc_start_main() UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago) UserGroups: adm lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/guvcview/+bug/1373221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416408] [NEW] Dialog shouldn't allow interactions with page behind it
Public bug reported: If you have an app that throws up a dialog, while the dialog is up, it shouldn't allow any interaction with the app. Normally, the dialog covers the whole page, so it's not really a problem. But if you turn your phone to landscape mode, the dialog stops covering the whole app and, for example, if you have an app with a PageStack and Pages, you can click on both the Page and the header widgets like the Back button. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1416408 Title: Dialog shouldn't allow interactions with page behind it Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: If you have an app that throws up a dialog, while the dialog is up, it shouldn't allow any interaction with the app. Normally, the dialog covers the whole page, so it's not really a problem. But if you turn your phone to landscape mode, the dialog stops covering the whole app and, for example, if you have an app with a PageStack and Pages, you can click on both the Page and the header widgets like the Back button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1416408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416408] Re: Dialog shouldn't allow interactions with page behind it
** Description changed: - If you have a app that throws up a dialog, while the dialog is up, it + If you have an app that throws up a dialog, while the dialog is up, it shouldn't allow any interaction with the app. Normally, the dialog covers the whole page, so it's not really a problem. But if you turn your phone to landscape mode, the dialog stops covering the whole app and, for example, if you have an app with a PageStack and Pages, you can click on both the Page and the header widgets like the Back button. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1416408 Title: Dialog shouldn't allow interactions with page behind it Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: If you have an app that throws up a dialog, while the dialog is up, it shouldn't allow any interaction with the app. Normally, the dialog covers the whole page, so it's not really a problem. But if you turn your phone to landscape mode, the dialog stops covering the whole app and, for example, if you have an app with a PageStack and Pages, you can click on both the Page and the header widgets like the Back button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1416408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416169] Re: İntel g41 ekran dalgalanma sorunu
** Description changed: - sublime text'de aşağı yukarı yaparken bir dalgalanma oluşuyor. - teşekkürler :) + açılışta sorun yaşıyorum. teşekkürler :) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .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 Date: Fri Jan 30 01:54:07 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: - Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) -Subsystem: Fujitsu Technology Solutions Device [1734:114c] + Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) + Subsystem: Fujitsu Technology Solutions Device [1734:114c] InstallationDate: Installed on 2015-01-29 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ARCELIK AS 1YA-ARCELIK 5440 ProcEnviron: - LANGUAGE=tr - PATH=(custom, no user) - LANG=tr_TR.UTF-8 - SHELL=/bin/bash + LANGUAGE=tr + PATH=(custom, no user) + LANG=tr_TR.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.02.3041.A1 dmi.board.name: D3041-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3041-A1 dmi.chassis.asset.tag: 93742010006534 dmi.chassis.type: 6 dmi.chassis.vendor: ARCELIK AS dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00R1.02.3041.A1:bd11/09/2010:svnARCELIKAS:pn1YA-ARCELIK5440:pvrV102:rvnFUJITSU:rnD3041-A1:rvrS26361-D3041-A1:cvnARCELIKAS:ct6:cvr: dmi.product.name: 1YA-ARCELIK 5440 dmi.product.version: V102 dmi.sys.vendor: ARCELIK AS 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.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: Fri Jan 30 01:40:43 2015 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputPower Button KEYBOARD, id 7 - inputHID 04f3:0103KEYBOARD, id 8 - inputHID 04f3:0103KEYBOARD, id 9 - inputSIGMACHIP Usb Mouse MOUSE, id 10 + inputPower Button KEYBOARD, id 6 + inputPower Button KEYBOARD, id 7 + inputHID 04f3:0103KEYBOARD, id 8 + inputHID 04f3:0103KEYBOARD, id 9 + inputSIGMACHIP Usb Mouse MOUSE, id 10 xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id2001 - vendor PTS + product id2001 + vendor PTS xserver.version: 2:1.16.0-1ubuntu1.2 ** Summary changed: - İntel g41 ekran dalgalanma sorunu + Ubuntu 14.10 Broken Pipe Hatası -- 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/1416169 Title: Ubuntu 14.10 Broken Pipe Hatası Status in xorg package in Ubuntu: New Bug description: açılışta sorun yaşıyorum. teşekkürler :) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .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 Date: Fri Jan 30 01:54:07 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Cor
[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
Updating to the latest xorg drivers using the xorg-edgers PPA seemed to have solved the slowness for me, but at the expense of stability -- from time to time I get complete system lockups. -- 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/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in xorg package in Ubuntu: New Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible "chops" (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: "I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway." Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A 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: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1286021] Re: 2.1 surround support (userspace)
I followed the instructs at https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1286021/comments/24, but I do not see an option for "Analog Surround 2.1 Output" in the Ubuntu Sound Settings with 14.10. How do I switch to that mode? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1286021 Title: 2.1 surround support (userspace) Status in alsa-lib package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Bug description: 2.1 surround should work as seamlessly as other surround options, such as 4.0, 5.1 and 7.1 work today. Alsa-lib and pulseaudio patches for 14.04 can be tested here: https://launchpad.net/~diwic/+archive/surround21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1286021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375756] Re: Weather scope is not detecting the correct location
** Tags added: usability -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1375756 Title: Weather scope is not detecting the correct location Status in the base for Ubuntu mobile products: Confirmed Status in unity-scopes-shell package in Ubuntu: New Status in unity-scopes-api package in Ubuntu RTM: New Bug description: It seems its using geoip so the automatically detected location is usually not correct, In my case its showing weather for a small city 90 miles away, Refreshing does not resolve it. The maps apps detect exact location. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1375756/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388235] Re: [indicators] Battery icon turns red at 30%
** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Milestone: None => ww07-2015 ** Tags added: usability -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1388235 Title: [indicators] Battery icon turns red at 30% Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Triaged Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-themes package in Ubuntu: In Progress Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416424] [NEW] Wifi list is empty
Public bug reported: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- 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/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413645] Re: [AV200 - Xonar DX, playback] Indicator-sound not starting
great, closing then ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => High ** Changed in: indicator-sound (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1413645 Title: [AV200 - Xonar DX, playback] Indicator-sound not starting Status in indicator-sound package in Ubuntu: Fix Released Bug description: Previously reported bug 1412060 against the indicator but that package got changed to pulseaudio - this was in a clean install. Booting from a livesession - I see exactly the same issue. Ran ubuntu-bug -s audio to pick up more sound related information. Sound works fine. Pavucontrol works fine. Pulseaudio is running ps aux |grep pulse xubuntu 2931 2.0 0.1 516896 11788 ?S LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DX successful Symptom_Card: Webcam C270 - USB Device 0x46d:0x825 Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [AV200 - Xonar DX, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1413645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416233] Re: Sound indicator notification shows each time the a sound starts or stops
Was about to post saying this is "by design" and link to the design, but it seems I missed a sentence at the end of the design: https://wiki.ubuntu.com/Sound#Output.2BAC8-volume_change_notification Where output role changes need to surpress the notifications. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1416233 Title: Sound indicator notification shows each time the a sound starts or stops Status in indicator-sound package in Ubuntu: New Bug description: The latest Vivid image on mako (84)[1] causes the sound notification to popup each time the system starts or stops a sound. When the sound stops the notification indicates that the sound is muted, when it is in fact not. In the Music app, for instance, this is quite annoying. 1 - http://people.canonical.com/~ogra/touch-image-stats/84.changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1416233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412060] Re: Indicator sound fails to start with Asus Xonar
great, closing then ** Changed in: indicator-sound (Ubuntu) Importance: Undecided => High ** Changed in: indicator-sound (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1412060 Title: Indicator sound fails to start with Asus Xonar Status in indicator-sound package in Ubuntu: Fix Released Bug description: Replaced Audigy with Xonar. Clean installed to new drive and partition. sound indicator fails to start upstart --user --startup-event indicator-services-start tries to start indicator - space in indicators shows where it is, clicking and menu doesn't appear ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20141105-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 17 21:37:27 2015 InstallationDate: Installed on 2015-01-09 (8 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1412060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416423] [NEW] Reviews should be in chronological order with most recent first
Public bug reported: I think it'd make more sense for reviews to be ordered chronologically with the most recent reviews first, as these are most likely to be relevant to the current version of an app (currently they appear to be unordered). ** Affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New ** Description changed: I think it'd make more sense for reviews to be ordered chronologically with the most recent reviews first, as these are most likely to be - relevant to the current version of an app. + relevant to the current version of an app (currently they appear to be + unordered). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1416423 Title: Reviews should be in chronological order with most recent first Status in unity-scope-click package in Ubuntu: New Bug description: I think it'd make more sense for reviews to be ordered chronologically with the most recent reviews first, as these are most likely to be relevant to the current version of an app (currently they appear to be unordered). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1416423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413747] Re: indicator-sound-service crashed with SIGSEGV in volume_control_sink_info_cb_for_props()
Thank you for your bug report, that should be resolved with that update https://launchpad.net/ubuntu/+source/indicator- sound/12.10.2+15.04.20150129.1-0ubuntu1 ** Information type changed from Private to Public ** Changed in: indicator-sound (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1413747 Title: indicator-sound-service crashed with SIGSEGV in volume_control_sink_info_cb_for_props() Status in indicator-sound package in Ubuntu: Fix Released Bug description: ref bug 1413645 and bug 1412060 set apport to report on crashes, unignored ind sound from /etc/apport/crashdb.conf restarted indicator-sound with upstart --user --startup-event indicator-services-start bug report resulting from that ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20141105-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: XFCE Date: Thu Jan 22 21:03:42 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-01-09 (13 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150108) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x411fa3: mov(%rax),%rdi PC (0x00411fa3) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-sound StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 Title: indicator-sound-service crashed with SIGSEGV in pa_pdispatch_run() 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/indicator-sound/+bug/1413747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1286021] Re: 2.1 surround support (userspace)
@Mike, maybe your sound card drivers do not show a subwoofer speaker? It's hard to tell without knowing your hardware (i e alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1286021 Title: 2.1 surround support (userspace) Status in alsa-lib package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Bug description: 2.1 surround should work as seamlessly as other surround options, such as 4.0, 5.1 and 7.1 work today. Alsa-lib and pulseaudio patches for 14.04 can be tested here: https://launchpad.net/~diwic/+archive/surround21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1286021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413269] Re: Qt network being unreliable establishing a connection
** Changed in: canonical-devices-system-image Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1413269 Title: Qt network being unreliable establishing a connection Status in the base for Ubuntu mobile products: Confirmed Status in qtbase-opensource-src package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu RTM: New Bug description: Qt network manager is unreliable as it sometimes reports the device being not online when in fact it is. This manifest in bugs like bug #1409995 or some scopes querying online resources just being empty. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all
Setting to incomplete while waiting for answers to comment #6 ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Incomplete ** Changed in: hwe-next Status: Confirmed => Incomplete -- 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/1414706 Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all Status in HWE Next Project: Incomplete Status in alsa-driver package in Ubuntu: Incomplete Bug description: During this test, an error dialog was thrown, reading: The following mixer control(s) might be incorrectly set: Mic is at 0.0% Mic is muted Please try to fix that (e g by running "alsamixer -D hw:PCH" in a terminal) and see if that solves the problem. Would you like to continue troubleshooting anyway? However, the System Settings... -> Sound UI shows the mic as not muted. When I tried running the alsamixer command, I saw mic and mic- boost were both showing 0; I cranked them up to 100, but it made no difference. I also tried re-running this command with the mic/mic- boost still set to 100 and it threw the same error. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 26 16:20:49 2015 InstallationDate: Installed on 2014-09-10 (138 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 1 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET75WW (2.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ALCTO1WW dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416293] Re: android container should not enable adb and mtp from default.prop
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Milestone: None => ww07-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1416293 Title: android container should not enable adb and mtp from default.prop Status in the base for Ubuntu mobile products: In Progress Status in lxc-android-config package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu RTM: In Progress Bug description: if the android container rootfs is built with ro.debuggable=1 it will put a default.prop file into the container rootfs with persist.sys.usb.config set to mtp,adb. on first boot after a factory flash (not using ubuntu-device-flash) when there was no value for this property set prior to starting the container this causes the gadget to be in adb mode without running adbd daemon. in his case the device will show up as "offline" in "adb devices" on a PC until developer mode was toggled once in the settings UI. lxc-android-config needs to ship a pre-start.d snippet that removes this entry from default.prop. this way recovery boots can still benefit from ro.debuggable being set while adb behavior will not be affected in normal boots. --- /var/lib/lxc/android/pre-start.d/20-no-default-prop-adb --- #! /bin/sh sed -i '/^persist.sys.usb.config=.*/d' $LXC_ROOTFS_PATH/default.prop --- To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416423] Re: Reviews should be in chronological order with most recent first
Good point. The server seems to be sending the "date_created" of each review, so there's little stopping the click scope from sorting before showing them. ** Changed in: unity-scope-click (Ubuntu) Importance: Undecided => High ** Changed in: unity-scope-click (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1416423 Title: Reviews should be in chronological order with most recent first Status in unity-scope-click package in Ubuntu: Triaged Bug description: I think it'd make more sense for reviews to be ordered chronologically with the most recent reviews first, as these are most likely to be relevant to the current version of an app (currently they appear to be unordered). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1416423/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 991666] Re: VPN Connects Successfully & Then Shortly Thereafter Fails
Hi all, I've experienced a very simmilar issue on 14.04 as well. The reason of my case actually was in routing table, in particular - routes pushed by VPN server. Those routes were wrong or interpreted incorrectly and some kind of packet collision was happening shortly after connecting VPN. More details described in my post - http://tdanas.blogspot.com/2015/01 /ubuntu-vpn-connects-successfully-and.html Regards, Danas -- 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/991666 Title: VPN Connects Successfully & Then Shortly Thereafter Fails Status in NetworkManager-PPTP: New Status in network-manager package in Ubuntu: Confirmed Bug description: I am able to successfully establish a PPTP VPN connection in Ubuntu 12.04 (kernel 3.2.0-24-generic) but after approximately 30 seconds to 1.5 minutes it will fail. During the connection time I am only able to load about 1-2 webpages and then they freeze and I cannot access resources on the VPN network. I do not believe this is related to my VPN server as I am able to establish VPN connections with my Windows machines and Smartphones all day long with no problems. Is there a solution to this problem? Description: Ubuntu 12.04 LTS Release: 12.04 network-manager: 0.9.4.0-0ubuntu3 Here is the syslog: Apr 30 00:17:50 satellite-p755 NetworkManager[994]: Starting VPN service 'pptp'... Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 15069 Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN service 'pptp' appeared; activating connections Apr 30 00:17:50 satellite-p755 NetworkManager[994]: VPN plugin state changed: starting (3) Apr 30 00:17:51 satellite-p755 NetworkManager[994]: VPN connection 'Schaefer Law Group' (Connect) reply received. Apr 30 00:17:51 satellite-p755 pppd[15073]: Plugin /usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded. Apr 30 00:17:51 satellite-p755 pppd[15073]: pppd 2.4.5 started by root, uid 0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Using interface ppp0 Apr 30 00:17:51 satellite-p755 pppd[15073]: Connect: ppp0 <--> /dev/pts/2 Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) Apr 30 00:17:51 satellite-p755 NetworkManager[994]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. Apr 30 00:17:51 satellite-p755 pptp[15076]: nm-pptp-service-15069 log[main:pptp.c:314]: The synchronous pptp option is NOT activated Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 'Start-Control-Connection-Request' Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply Apr 30 00:17:51 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established. Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 'Outgoing-Call-Request' Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply. Apr 30 00:17:52 satellite-p755 pptp[15084]: nm-pptp-service-15069 log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's call ID 0). Apr 30 00:17:55 satellite-p755 pppd[15073]: CHAP authentication succeeded Apr 30 00:17:55 satellite-p755 pppd[15073]: MPPE 128-bit stateless compression enabled Apr 30 00:17:55 satellite-p755 pppd[15073]: local IP address 192.168.1.20 Apr 30 00:17:55 satellite-p755 pppd[15073]: remote IP address 192.168.1.1 Apr 30 00:17:55 satellite-p755 pppd[15073]: primary DNS address 8.8.8.8 Apr 30 00:17:55 satellite-p755 pppd[15073]: secondary DNS address 8.8.4.4 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: VPN connection 'Schaefer Law Group' (IP Config Get) reply received. Apr 30 00:17:55 satellite-p755 NetworkManager[994]: VPN Gateway: 75.75.79.330 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Tunnel Device: ppp0 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 Address: 192.168.1.20 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 Prefix: 32 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 Point-to-Point Address: 192.168.1.1 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Maximum Segment Size (MSS): 0 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Forbid Default Route: no Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 DNS: 8.8.8.8 Apr 30 00:17:55 satellite-p755 NetworkManager[994]: Internal IP4 DNS: 8.8.
[Touch-packages] [Bug 1324000] Re: Re-enable qtbase tests that are disabled with Qt 5.3
** Changed in: qtbase-opensource-src (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1324000 Title: Re-enable qtbase tests that are disabled with Qt 5.3 Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: To get Qt 5.3 builds going, I had to disable qtbase tests at first. I've now worked on restoring them, but while doing so a handful of new failing tests were discovered that I had to disable. These newly disabled tests should be re-enabled. The commit where tests were re-enabled but some tests disabled was: http://bazaar.launchpad.net/~timo-jyrinki/kubuntu-packaging/qtbase- opensource-src_qt530RC/revision/175 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1324000/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416441] [NEW] package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Got error during upgrade. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: gnome-icon-theme 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic i686 ApportVersion: 2.15.1-0ubuntu4 Architecture: i386 Date: Fri Jan 30 17:03:37 2015 DuplicateSignature: package:gnome-icon-theme:3.12.0-1ubuntu1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-07-19 (559 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) PackageArchitecture: all SourcePackage: gnome-icon-theme Title: package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to vivid on 2014-09-26 (125 days ago) ** Affects: gnome-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1416441 Title: package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-icon-theme package in Ubuntu: New Bug description: Got error during upgrade. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: gnome-icon-theme 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic i686 ApportVersion: 2.15.1-0ubuntu4 Architecture: i386 Date: Fri Jan 30 17:03:37 2015 DuplicateSignature: package:gnome-icon-theme:3.12.0-1ubuntu1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-07-19 (559 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) PackageArchitecture: all SourcePackage: gnome-icon-theme Title: package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to vivid on 2014-09-26 (125 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1416441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
This happens to me at least once every day, each time the whole session, open windows and unsaved documents lost (I save, yes, but the fact that at any time things can be lost makes this a critical issue for me). Is there a chance this can 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/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 versi
[Touch-packages] [Bug 1416441] Re: package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1416441 Title: package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in gnome-icon-theme package in Ubuntu: New Bug description: Got error during upgrade. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: gnome-icon-theme 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic i686 ApportVersion: 2.15.1-0ubuntu4 Architecture: i386 Date: Fri Jan 30 17:03:37 2015 DuplicateSignature: package:gnome-icon-theme:3.12.0-1ubuntu1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-07-19 (559 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) PackageArchitecture: all SourcePackage: gnome-icon-theme Title: package gnome-icon-theme 3.12.0-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to vivid on 2014-09-26 (125 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1416441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1081607] Re: Provide translations for the text used in the SDK that will be visible for the user
It seems that the translations for lp:ubuntu-ui-toolkit are not being merged
from launchpad.
eg, the "In progress" text shown in the progressbar is not translated into
spanish, even when it seems to be translated in launchpad:
https://translations.launchpad.net/ubuntu-ui-toolkit/trunk/+pots/ubuntu-ui-toolkit/es/+translate?memo=20&start=20
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1081607
Title:
Provide translations for the text used in the SDK that will be visible
for the user
Status in the base for Ubuntu mobile products:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
For example, DefaultSheet currently has buttons with text:
text: i18n.dtr("ubuntu-sdk", "close"), and
text: i18n.dtr("ubuntu-sdk", "done")
but there are other text-occurences that need to be translated.
We need to provide .po and .mo files for translations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1081607/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416451] [NEW] Can't switch display mode more than one cycle when docked
Public bug reported: [Impact] We have a system under certification that needs a workaround in the kernel for now. The bug is that if the machine is booted attached to a dock with a monitor connected to it's VGA output, the connection to the monitor is dropped after one full cycle of display modes with the hotkey combo. This is a firmware bug and will eventually be fixed by the BIOS vendor, but in the meantime we need a workaround in the kernel. The dock has a builtin DP-VGA dongle which is the culprit here. [Test Case] attach the unit to a doc with a monitor plugged to a VGA port, switch display modes with hotkey combo, should be able to do more than one cycle with the combo [Regression Potential] We got the patch from Intel, with this disclaimer: "The workaround in comment 41# maybe has side effect on DP port which doesn't connect DP screen. On these DP ports, this workaround will add an extra power on and power off command . So this workaround couldn't push to upstream." so there shouldn't be any visible regressions.. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: Triaged ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: linux (Ubuntu) Status: New => Triaged -- 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/1416451 Title: Can't switch display mode more than one cycle when docked Status in linux package in Ubuntu: Triaged Bug description: [Impact] We have a system under certification that needs a workaround in the kernel for now. The bug is that if the machine is booted attached to a dock with a monitor connected to it's VGA output, the connection to the monitor is dropped after one full cycle of display modes with the hotkey combo. This is a firmware bug and will eventually be fixed by the BIOS vendor, but in the meantime we need a workaround in the kernel. The dock has a builtin DP-VGA dongle which is the culprit here. [Test Case] attach the unit to a doc with a monitor plugged to a VGA port, switch display modes with hotkey combo, should be able to do more than one cycle with the combo [Regression Potential] We got the patch from Intel, with this disclaimer: "The workaround in comment 41# maybe has side effect on DP port which doesn't connect DP screen. On these DP ports, this workaround will add an extra power on and power off command . So this workaround couldn't push to upstream." so there shouldn't be any visible regressions.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416451/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1081607] Re: Provide translations for the text used in the SDK that will be visible for the user
I believe this bug should be Critical by now, can you guys please
reasses its importance?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1081607
Title:
Provide translations for the text used in the SDK that will be visible
for the user
Status in the base for Ubuntu mobile products:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
For example, DefaultSheet currently has buttons with text:
text: i18n.dtr("ubuntu-sdk", "close"), and
text: i18n.dtr("ubuntu-sdk", "done")
but there are other text-occurences that need to be translated.
We need to provide .po and .mo files for translations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1081607/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416450] [NEW] [regression] Tab switcher doesn't work if a text field is focused
Public bug reported:
Steps to reproduce:
1) Run the following QML:
import QtQuick 2.0
import Ubuntu.Components 1.0
MainView {
useDeprecatedToolbar: false
anchorToKeyboard: true
Tabs {
Tab {
title: "Test"
Page {
title: "Test"
TextField {
anchors.centerIn: parent
}
}
}
Tab {
title: "Test 2"
Page {
title: "Test 2"
}
}
}
}
2) Tap the input field
3) Tap the tab switcher
Expected outcome:
Tab menu should appear
Actual outcome:
Tab menu doesn't appear unless the keyboard is dismissed first (which
removes input focus from the field).
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1416450
Title:
[regression] Tab switcher doesn't work if a text field is focused
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
Steps to reproduce:
1) Run the following QML:
import QtQuick 2.0
import Ubuntu.Components 1.0
MainView {
useDeprecatedToolbar: false
anchorToKeyboard: true
Tabs {
Tab {
title: "Test"
Page {
title: "Test"
TextField {
anchors.centerIn: parent
}
}
}
Tab {
title: "Test 2"
Page {
title: "Test 2"
}
}
}
}
2) Tap the input field
3) Tap the tab switcher
Expected outcome:
Tab menu should appear
Actual outcome:
Tab menu doesn't appear unless the keyboard is dismissed first (which
removes input focus from the field).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1416450/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416450] Re: [regression] Tab switcher doesn't work if a text field is focused
This is present on vivid-proposed image #84 and doesn't exist on RTM.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1416450
Title:
[regression] Tab switcher doesn't work if a text field is focused
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
Steps to reproduce:
1) Run the following QML:
import QtQuick 2.0
import Ubuntu.Components 1.0
MainView {
useDeprecatedToolbar: false
anchorToKeyboard: true
Tabs {
Tab {
title: "Test"
Page {
title: "Test"
TextField {
anchors.centerIn: parent
}
}
}
Tab {
title: "Test 2"
Page {
title: "Test 2"
}
}
}
}
2) Tap the input field
3) Tap the tab switcher
Expected outcome:
Tab menu should appear
Actual outcome:
Tab menu doesn't appear unless the keyboard is dismissed first (which
removes input focus from the field).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1416450/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416424] Re: Wifi list is empty
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+attachment/4308867/+files/syslog -- 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/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416424] Re: Wifi list is empty
phablet@ubuntu-phablet:~$ nmcli dev wifi list * SSIDMODE CHAN RATE SIGNAL BARS SECURITY davmor2 Infra 1 54 Mbit/s 100 ▂▄▆█ WPA1 WPA2 davmor2-5g Infra 4054 Mbit/s 97 ▂▄▆█ WPA1 WPA2 SKY31983Infra 6 54 Mbit/s 19 ▂___ WPA2 virginmedia5828324 Infra 1154 Mbit/s 17 ▂___ WPA1 WPA2 Segmentation fault (core dumped) ** Tags added: qa-sanity -- 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/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416424] Re: Wifi list is empty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416424] Re: Wifi list is empty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-network (Ubuntu) Status: New => Confirmed -- 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/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416424] Re: Wifi list is empty
** Attachment added: "wifi-84.png" https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+attachment/4308869/+files/wifi-84.png -- 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/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416424] Re: Wifi list is empty
** Description changed: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. + + phablet@ubuntu-phablet:~$ system-image-cli -i + current build number: 84 + device name: mako + channel: ubuntu-touch/devel-proposed + alias: ubuntu-touch/vivid-proposed + last update: 2015-01-30 14:45:36 + version version: 84 + version ubuntu: 20150130 + version device: 20150129 + version custom: 20150130 -- 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/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392187] Re: the "Log out" and "Shut down" menu show the same Log-Out dialog
** Branch linked: lp:~townsend/unity8/fix-lp1392187 -- 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/1392187 Title: the "Log out" and "Shut down" menu show the same Log-Out dialog Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Triaged Bug description: the "Log out" and "Shut down" menu show the same Log-Out dialog, and when confirmed to log out or shut down, they all just go back to greeter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1392187/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415976] Re: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Do you have the libc-bin package installed? ** Changed in: initramfs-tools (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1415976 Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: error return after running apt-get upgrade, either do update-grub or apt-get autoremove ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: lincoln2691 F...m pulseaudio /dev/snd/pcmC0D0p: lincoln2691 F...m pulseaudio /dev/snd/controlC0: lincoln2691 F pulseaudio Date: Thu Jan 29 17:05:17 2015 DuplicateSignature: package:linux-image-3.16.0-25-generic:3.16.0-25.33:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=47ef734d-36c6-4152-8563-b87503b06b2f InstallationDate: Installed on 2014-10-23 (97 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire S3-391 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic.efi.signed root=UUID=52a1760e-8bce-400d-978a-b4a1df8b94f5 ro quiet splash acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd09/12/2012:svnAcer:pnAspireS3-391:pvrV2.09:rvnAcer:rnHummingbird2:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.name: Aspire S3-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1415976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416074] Re: The Unity 8 desktop session dialogs should match what is done in Unity 7
** Branch linked: lp:~townsend/unity8/fix-lp1416074 -- 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/1416074 Title: The Unity 8 desktop session dialogs should match what is done in Unity 7 Status in unity8 package in Ubuntu: New Bug description: In Unity 7, when you click Log Out in indicator-session, a dialog pops up to ask if the user would like to either Lock the machine or Log Out. Similarly, when Shut Down is chosen, the dialog asks the user to either Reboot or Shut Down. Currently, in the Unity 8 desktop, indicator-session still only show Log Out and Shut Down, so Reboot is not even possible. I think Unity 8 should display similar dialogs and offer the same actions as Unity 7, at least for now until we get new input from Design. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1416074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360316] Re: Logging out the desktop session just goes back to the Unity 8 Session Greeter
** Changed in: unity8 (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1360316 Title: Logging out the desktop session just goes back to the Unity 8 Session Greeter Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: When trying to log out of the desktop session, you are taken back to the Unity 8 Session Greeter. The desired behavior should be to go back to the LightDM greeter when logging out. This is with version 8.00+14.10.20140822-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415976] Re: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
>From DpkgTerminalLog.txt: update-initramfs: Generating /boot/initrd.img-3.16.0-24-generic WARNING: no ldd around - install libc-bin update-initramfs: failed for /boot/initrd.img-3.16.0-24-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1415976 Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: error return after running apt-get upgrade, either do update-grub or apt-get autoremove ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: lincoln2691 F...m pulseaudio /dev/snd/pcmC0D0p: lincoln2691 F...m pulseaudio /dev/snd/controlC0: lincoln2691 F pulseaudio Date: Thu Jan 29 17:05:17 2015 DuplicateSignature: package:linux-image-3.16.0-25-generic:3.16.0-25.33:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=47ef734d-36c6-4152-8563-b87503b06b2f InstallationDate: Installed on 2014-10-23 (97 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire S3-391 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic.efi.signed root=UUID=52a1760e-8bce-400d-978a-b4a1df8b94f5 ro quiet splash acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd09/12/2012:svnAcer:pnAspireS3-391:pvrV2.09:rvnAcer:rnHummingbird2:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.name: Aspire S3-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1415976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310316] Re: Text scaling factor changing unexpectedly
Also affected, mostly scaling factor goes up to 3, try to change with gnome-tweak-tool or unity-tweak-tool without any afford. Ubuntu 14.04, beside Google Chrome no extra PPAs MSI Adora22 (Intel Core i3 4100M, Intel HD-Grafik 4600) Here you can find a workaround: http://askubuntu.com/questions/469515/adjust-text-scaling-factor-for-all-users But this is no solution at all, there must be a bug somewhere. -- 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/1310316 Title: Text scaling factor changing unexpectedly Status in Unity: Confirmed Status in unity package in Ubuntu: Incomplete Bug description: I have a MacBook pro with a Retina display. I have set the "Scale for menu and title bars" setting (into Settings > Displays) to 1.5 to make the UI looks good on my screen. That works very well. But sometimes, usually after logging, all the fonts of the UI become much bigger. When that happen I open unity tweat tool and notice that the text scaling factor changed to 2.25. If I reset it to 1 the all the fonts go back to normal. The problem does not happen all the time. I would say it happen one time out of three logging. It may also happen when installing applications from the software center. I have yet to find a procedure to reproduce it all the times. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 20 18:21:02 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00f2] InstallationDate: Installed on 2014-04-19 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3d5a4115-5e15-4eca-bd1c-0bee2543a1cb ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-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-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Apr 20 18:04:05 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1310316/+subscriptions -- Mailing list: https://launchpad.net/~touch
Re: [Touch-packages] [Bug 1415976] Re: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Pardon, I just reinstalled Ubuntu for necessity. Problem is no longer showing up. On Fri, Jan 30, 2015, 17:05 Brian Murray wrote: > Do you have the libc-bin package installed? > > ** Changed in: initramfs-tools (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1415976 > > Title: > package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to > install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools > exited with return code 1 > > Status in initramfs-tools package in Ubuntu: > Incomplete > > Bug description: > error return after running apt-get upgrade, either do update-grub or > apt-get autoremove > > ProblemType: Package > DistroRelease: Ubuntu 14.10 > Package: linux-image-3.16.0-25-generic 3.16.0-25.33 > 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.1 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/pcmC0D0c: lincoln2691 F...m pulseaudio >/dev/snd/pcmC0D0p: lincoln2691 F...m pulseaudio >/dev/snd/controlC0: lincoln2691 F pulseaudio > Date: Thu Jan 29 17:05:17 2015 > DuplicateSignature: package:linux-image-3.16.0-25- > generic:3.16.0-25.33:run-parts: /etc/kernel/postinst.d/initramfs-tools > exited with return code 1 > ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited > with return code 1 > HibernationDevice: RESUME=UUID=47ef734d-36c6-4152-8563-b87503b06b2f > InstallationDate: Installed on 2014-10-23 (97 days ago) > InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 > (20141022.1) > MachineType: Acer Aspire S3-391 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic.efi.signed > root=UUID=52a1760e-8bce-400d-978a-b4a1df8b94f5 ro quiet splash > acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: grub-pc N/A > SourcePackage: initramfs-tools > Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to > install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited > with return code 1 > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/12/2012 > dmi.bios.vendor: Insyde Corp. > dmi.bios.version: V2.09 > dmi.board.asset.tag: Type2 - Board Asset Tag > dmi.board.name: Hummingbird2 > dmi.board.vendor: Acer > dmi.board.version: V2.09 > dmi.chassis.asset.tag: Chassis Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: V2.09 > dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd09/12/2012:svnAcer: > pnAspireS3-391:pvrV2.09:rvnAcer:rnHummingbird2:rvrV2. > 09:cvnAcer:ct10:cvrV2.09: > dmi.product.name: Aspire S3-391 > dmi.product.version: V2.09 > dmi.sys.vendor: Acer > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1415976/+ > subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1415976 Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Incomplete Bug description: error return after running apt-get upgrade, either do update-grub or apt-get autoremove ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: lincoln2691 F...m pulseaudio /dev/snd/pcmC0D0p: lincoln2691 F...m pulseaudio /dev/snd/controlC0: lincoln2691 F pulseaudio Date: Thu Jan 29 17:05:17 2015 DuplicateSignature: package:linux-image-3.16.0-25-generic:3.16.0-25.33:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=47ef734d-36c6-4152-8563-b87503b06b2f InstallationDate: Installed on 2014-10-23 (97 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire S3-391 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic.efi.signed root=UUID=52a1760e-8bce-400d-978a-b4a1df8b94f5 ro quiet splash acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handof
[Touch-packages] [Bug 1372413] Re: Extensive battery drain on RTM
** Changed in: canonical-devices-system-image Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1372413 Title: Extensive battery drain on RTM Status in the base for Ubuntu mobile products: In Progress Status in powerd package in Ubuntu: Confirmed Bug description: Mako, RTM 1 Since upgrading to RTM the battery life is really poor. What used to be a battery drain of 5-10% per hour (which is still high) is now 10-15% per hour. Sometimes the phone runs really hot, so there seem to be something going on in the background that is consuming power. I mostly have bluetooth, GPS (which isn't always working), wifi and cellular on, but that's no difference from when I was running 'devel- proposed' with MultiROM with much less battery consumption. As an example, I started with a full charge at 7am. After some web surfing (<15 mins) and watching a couple of youtube videos (on wifi) battery was down to 66% at 9:15. That's 34% in just over two hours! I recharged again before lunch and had the phone idle until coming back 1 hour and 45 mins later to find only 75% of battery left, this time without the phone running particularly hot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414925] Re: ntpd seems to add offsets instead of subtracting them
** Changed in: ntp (Ubuntu) Assignee: (unassigned) => Liam Young (gnuoy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1414925 Title: ntpd seems to add offsets instead of subtracting them Status in ntp package in Ubuntu: New Status in ntp package in CentOS: New Status in ntp package in Debian: New Bug description: ntpd seems to add offsets instead of subtracting them from the running synchronized clock, leading to time running away fast in one direction -- forward if the offset is positive, -- backward if the offset is negative, until the offset reaches its maximum. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 27 08:25:55 2015 InstallationDate: Installed on 2014-02-10 (350 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) KernLog: NtpStatus: ntpq: read: Connection refused ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: Upgraded to trusty on 2014-02-18 (342 days ago) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2015-01-27T07:41:51.747605 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1414925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415976] Re: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1415976 Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: error return after running apt-get upgrade, either do update-grub or apt-get autoremove ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: lincoln2691 F...m pulseaudio /dev/snd/pcmC0D0p: lincoln2691 F...m pulseaudio /dev/snd/controlC0: lincoln2691 F pulseaudio Date: Thu Jan 29 17:05:17 2015 DuplicateSignature: package:linux-image-3.16.0-25-generic:3.16.0-25.33:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=47ef734d-36c6-4152-8563-b87503b06b2f InstallationDate: Installed on 2014-10-23 (97 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire S3-391 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic.efi.signed root=UUID=52a1760e-8bce-400d-978a-b4a1df8b94f5 ro quiet splash acpi_osi=Linux acpi_backlight=vendor quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd09/12/2012:svnAcer:pnAspireS3-391:pvrV2.09:rvnAcer:rnHummingbird2:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.name: Aspire S3-391 dmi.product.version: V2.09 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1415976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1277245] Re: nvidia prime causing mouse and screen to freeze
I have the same issues here uname -a : Linux felix-G551JM 3.16.0-29-generic #39-Ubuntu SMP Mon Dec 15 22:27:29 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux lspci | ergrep -i "vga|3d" 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 860M] (rev a2) cat /etc/lsb-release : DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.10 DISTRIB_CODENAME=utopic DISTRIB_DESCRIPTION="Ubuntu 14.10" nvidia-331 -- 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/1277245 Title: nvidia prime causing mouse and screen to freeze Status in xorg package in Ubuntu: Incomplete Bug description: I upgraded to Ubuntu Trusty Tahr . Currently running with updates as of 6th Feb. 64bit. After installing nvidia-prime and nvidia-331, i can see frequent mouse freezes. Once the mouse is frozen, it doesn't allow Alt+Tab functionality. Only way to get out of this is by pressing Ctrl+Alt+F1 . I can bring back by unloading and loading the psmouse module modprobe -r psmouse. lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) 01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) uname -a Linux Vostro-3300 3.13.0-6-generic #23-Ubuntu SMP Thu Jan 30 09:48:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)" This issue does not occur while running the opensource driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1277245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1081607] Re: Provide translations for the text used in the SDK that will be visible for the user
I bumped up bug #1391617 which has the fix already in vivid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1081607
Title:
Provide translations for the text used in the SDK that will be visible
for the user
Status in the base for Ubuntu mobile products:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
For example, DefaultSheet currently has buttons with text:
text: i18n.dtr("ubuntu-sdk", "close"), and
text: i18n.dtr("ubuntu-sdk", "done")
but there are other text-occurences that need to be translated.
We need to provide .po and .mo files for translations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1081607/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416424] Re: Wifi list is empty
Thank you, Dave. :) -- 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/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378774] Re: Swipe to delete is not translatable
this is fixed in RTM since r1115. ** Changed in: ubuntu-ui-toolkit (Ubuntu RTM) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1378774 Title: Swipe to delete is not translatable Status in Ubuntu UI Toolkit: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: Fix Released Bug description: See the attached screenshot. Upon receiving a push notification on the indicator, if I try to right swipe to delete it, the "Delete" text is not translated. It appears not to be translatable in Launchpad, so probably it needs to be marked for translation or the .pot file needs update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1378774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Hello, Same problem here after doing an upgrade from 12.04 to 14.04. On the affected machine, some users (basically admins) have both unix accounts and LDAP accounts. Users with both accounts can log in with unix or ldap password. However, when the desktop is locked, the only way to unlock is to use a unix password. I've tried unix_chkpwd suid workaround (no success) and checked /etc/shadow file permissions (was ok). I'm using libpam-ldap. -- 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/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "user" Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info (user) Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info (user) Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "user" cat /etc/pam.d/common-auth account requiredpam_unix.so authrequiredpam_group.so auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200 authrequisite pam_deny.so authrequiredpam_permit.so authoptionalpam_afs_session.so minimum_uid=200 authoptionalpam_ecryptfs.so unwrap authoptionalpam_cap.so cat /etc/pam.d/common-account account requiredpam_unix.so cat /etc/pam.d/lightdm authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close authoptionalpam_group.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optionalpam_gnome_keyring.so auto_start session requiredpam_env.so readenv=1 session requiredpam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale @include common-password To manage notifications about this bug go to: https://bugs.launchpad.net/
[Touch-packages] [Bug 1081607] Re: Provide translations for the text used in the SDK that will be visible for the user
I did a grep on i18n.tr in UITK components and none of those were found
(except in the examples of the component documentation, where it is
good). So I think this bug can be closed now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1081607
Title:
Provide translations for the text used in the SDK that will be visible
for the user
Status in the base for Ubuntu mobile products:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
For example, DefaultSheet currently has buttons with text:
text: i18n.dtr("ubuntu-sdk", "close"), and
text: i18n.dtr("ubuntu-sdk", "done")
but there are other text-occurences that need to be translated.
We need to provide .po and .mo files for translations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1081607/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416096] Re: expose battery charging state on the bus
** Branch linked: lp:~charlesk/indicator-power/lp-1416096-publish- primary-device-state-on-bus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1416096 Title: expose battery charging state on the bus Status in the base for Ubuntu mobile products: Confirmed Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in indicator-power package in Ubuntu RTM: Confirmed Status in ubuntu-system-settings package in Ubuntu RTM: Confirmed Bug description: Requested by kenvandine in #ubuntu-touch on freenode for u-s-s to show the right battery status. He needs it for bug 1329702. Since that's a proprietary bug that can't affect multiple projects, this is a separately filed ticket. Since this for the qml in u-s-s, this should be a GAction state similar to how auto-brightness' state is exposed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1081607] Re: Provide translations for the text used in the SDK that will be visible for the user
** Branch linked: lp:~tpeeters/ubuntu-ui-toolkit/rtm-translations
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1081607
Title:
Provide translations for the text used in the SDK that will be visible
for the user
Status in the base for Ubuntu mobile products:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
For example, DefaultSheet currently has buttons with text:
text: i18n.dtr("ubuntu-sdk", "close"), and
text: i18n.dtr("ubuntu-sdk", "done")
but there are other text-occurences that need to be translated.
We need to provide .po and .mo files for translations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1081607/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1081607] Re: Provide translations for the text used in the SDK that will be visible for the user
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1081607
Title:
Provide translations for the text used in the SDK that will be visible
for the user
Status in the base for Ubuntu mobile products:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
For example, DefaultSheet currently has buttons with text:
text: i18n.dtr("ubuntu-sdk", "close"), and
text: i18n.dtr("ubuntu-sdk", "done")
but there are other text-occurences that need to be translated.
We need to provide .po and .mo files for translations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1081607/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415140] Re: fullscreen mode should be dynamic
** Branch linked: lp:~artmello/gallery-app/gallery-app- fullscreen_on_device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1415140 Title: fullscreen mode should be dynamic Status in the base for Ubuntu mobile products: New Status in Gallery App: In Progress Status in gallery-app package in Ubuntu: New Status in gallery-app package in Ubuntu RTM: New Bug description: on touch, gallery is launched in fullscreen mode because previously there wasn't a way to dynamically toggle between fullscreen mode for different views within the app. The desired behavior on touch would be the following: - Don't launch app in fullscreen mode by default - Switch to fullscreen mode when viewing a photo (i.e. in slideshow mode) - When tapping on the photo to display the header we should switch out of fullscreen mode I think basically the rule would be when the header is visible we are not fullscreen and when the header is hidden (i.e. viewing pictures) the app should be in fullscreen. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1081607] Re: Provide translations for the text used in the SDK that will be visible for the user
It appears that the "In Progress" text was the only translation missing.
I will close this bug as well when the "In Progress" fix lands in RTM.
Please report separate bugs for other missing translations.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1081607
Title:
Provide translations for the text used in the SDK that will be visible
for the user
Status in the base for Ubuntu mobile products:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
For example, DefaultSheet currently has buttons with text:
text: i18n.dtr("ubuntu-sdk", "close"), and
text: i18n.dtr("ubuntu-sdk", "done")
but there are other text-occurences that need to be translated.
We need to provide .po and .mo files for translations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1081607/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415140] Re: fullscreen mode should be dynamic
** Changed in: gallery-app Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1415140 Title: fullscreen mode should be dynamic Status in the base for Ubuntu mobile products: New Status in Gallery App: In Progress Status in gallery-app package in Ubuntu: New Status in gallery-app package in Ubuntu RTM: New Bug description: on touch, gallery is launched in fullscreen mode because previously there wasn't a way to dynamically toggle between fullscreen mode for different views within the app. The desired behavior on touch would be the following: - Don't launch app in fullscreen mode by default - Switch to fullscreen mode when viewing a photo (i.e. in slideshow mode) - When tapping on the photo to display the header we should switch out of fullscreen mode I think basically the rule would be when the header is visible we are not fullscreen and when the header is hidden (i.e. viewing pictures) the app should be in fullscreen. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416096] Re: expose battery charging state on the bus
** Branch linked: lp:~charlesk/indicator-power/lp-1416096-publish- primary-device-state-on-bus-15.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1416096 Title: expose battery charging state on the bus Status in the base for Ubuntu mobile products: Confirmed Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in indicator-power package in Ubuntu RTM: Confirmed Status in ubuntu-system-settings package in Ubuntu RTM: Confirmed Bug description: Requested by kenvandine in #ubuntu-touch on freenode for u-s-s to show the right battery status. He needs it for bug 1329702. Since that's a proprietary bug that can't affect multiple projects, this is a separately filed ticket. Since this for the qml in u-s-s, this should be a GAction state similar to how auto-brightness' state is exposed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416424] Re: Wifi list is empty
OTA upgrading from 81 (Last known working image) to 84 leads to a Working auto connect system but you can not connect to a new network. ** Attachment added: "wifi-broken-but-connected.png" https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+attachment/4308891/+files/wifi-broken-but-connected.png -- 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/1416424 Title: Wifi list is empty Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: On recent vivid-proposed builds for mako (e.g. r83), the Wifi list in the network indicator as well as in the system settings is empty, even when the phone has automatically connected to a saved network. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 84 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-01-30 14:45:36 version version: 84 version ubuntu: 20150130 version device: 20150129 version custom: 20150130 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1416424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416485] [NEW] show place holder in message when recv unsupported MMS attachements
Public bug reported: krillin build 224 When we recieve an MMS attachment of a type we don't know how to handle, we should show some sort of default icon/message saying attachment type not supported. Currently we don't display anything so the user gets a blank message. Steps to reproduce: - send a .wav file or some other format to Ubuntu Phone that it doesn't know how to handle Expected results: - I receive the message in the messaging app with a notice that the attachment received cannot be viewed Actual results: - I'm notified of a message but the message is completely blank ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: messaging-app Importance: High Status: New ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Affects: messaging-app (Ubuntu RTM) Importance: Undecided Status: New ** Tags: ww07 ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Also affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Also affects: messaging-app (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: messaging-app Importance: Undecided => High ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Tags added: ww07 -- 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/1416485 Title: show place holder in message when recv unsupported MMS attachements Status in the base for Ubuntu mobile products: New Status in Messaging App: New Status in Ubuntu UX bugs: New Status in messaging-app package in Ubuntu: New Status in messaging-app package in Ubuntu RTM: New Bug description: krillin build 224 When we recieve an MMS attachment of a type we don't know how to handle, we should show some sort of default icon/message saying attachment type not supported. Currently we don't display anything so the user gets a blank message. Steps to reproduce: - send a .wav file or some other format to Ubuntu Phone that it doesn't know how to handle Expected results: - I receive the message in the messaging app with a notice that the attachment received cannot be viewed Actual results: - I'm notified of a message but the message is completely blank To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414740] Re: [phone-app] Multiple calls text delegate overlapping
** Changed in: dialer-app Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1414740 Title: [phone-app] Multiple calls text delegate overlapping Status in Dialer app for Ubuntu Touch: In Progress Status in Ubuntu UX bugs: Fix Committed Status in dialer-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu RTM: New Bug description: In the multiple calls screen, depending on the language and on the contact name labels are overlapping. Check the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1414740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415023] Re: sim unlock/lock confirmation button dismisses keybaord but doesn't confirm till pressed again
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1415023 Title: sim unlock/lock confirmation button dismisses keyboard but doesn't confirm till pressed again Status in ubuntu-system-settings package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: STEPS: Setup: 1 phone + one locked sim 1. Open system settings 2. Goto Security 3. Goto Sim Pin 4. Tap on unlock 5. Type in the pin 6. Tap the green confirm button EXPECTED: I expect the dialog to be dismissed and the keyboard and sim be unlocked ACTUAL: The keyboard is dismissed but the dialog box remains. A recent change has effected this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1415023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325110] Re: Audacity HEAD shows almost no shortcuts in menus using Unity
A workaround has been committed at https://code.google.com/p/audacity/source/detail?r=13894 so that src/audacity.desktop.in is set to UBUNTU_MENUPROXY=0. Audacity compiled from source will thus show shortcuts in the menus and will have its own menu bar in the application. It will remain up to Ubuntu whether they use this desktop file in packaged versions of Audacity. -- 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/1325110 Title: Audacity HEAD shows almost no shortcuts in menus using Unity Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Observed in Audacity r13166 in Ubuntu 14.04 using Unity with Ambience or Radiance theme. Only the shortcuts for Edit > Undo and Redo are visible in the menus. I do not experience inactive menus mentioned in https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1312625 . Initialising audacity.cfg does not help. The shortcuts appear in the menus when using Gnome flashback ( http://www.omgubuntu.co.uk/2014/04/ubuntu-14-04-classic-gnome- flashback-session ). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1325110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415023] Re: sim unlock/lock confirmation button dismisses keybaord but doesn't confirm till pressed again
Depending on the fix may backport to rtm ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Zsombor Egri (zsombi) ** Summary changed: - sim unlock/lock confirmation button dismisses keybaord but doesn't confirm till pressed again + sim unlock/lock confirmation button dismisses keyboard but doesn't confirm till pressed again -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1415023 Title: sim unlock/lock confirmation button dismisses keyboard but doesn't confirm till pressed again Status in ubuntu-system-settings package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: STEPS: Setup: 1 phone + one locked sim 1. Open system settings 2. Goto Security 3. Goto Sim Pin 4. Tap on unlock 5. Type in the pin 6. Tap the green confirm button EXPECTED: I expect the dialog to be dismissed and the keyboard and sim be unlocked ACTUAL: The keyboard is dismissed but the dialog box remains. A recent change has effected this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1415023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416096] Re: expose battery charging state on the bus
** Branch linked: lp:~ken-vandine/ubuntu-system- settings/lp1329702_battery_charging_status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1416096 Title: expose battery charging state on the bus Status in the base for Ubuntu mobile products: Confirmed Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in indicator-power package in Ubuntu RTM: Confirmed Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Bug description: Requested by kenvandine in #ubuntu-touch on freenode for u-s-s to show the right battery status. He needs it for bug 1329702. Since that's a proprietary bug that can't affect multiple projects, this is a separately filed ticket. Since this for the qml in u-s-s, this should be a GAction state similar to how auto-brightness' state is exposed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416096] Re: expose battery charging state on the bus
** Changed in: ubuntu-system-settings (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-system-settings (Ubuntu RTM) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1416096 Title: expose battery charging state on the bus Status in the base for Ubuntu mobile products: Confirmed Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in indicator-power package in Ubuntu RTM: Confirmed Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Bug description: Requested by kenvandine in #ubuntu-touch on freenode for u-s-s to show the right battery status. He needs it for bug 1329702. Since that's a proprietary bug that can't affect multiple projects, this is a separately filed ticket. Since this for the qml in u-s-s, this should be a GAction state similar to how auto-brightness' state is exposed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416096] Re: expose battery charging state on the bus
** Branch linked: lp:~ken-vandine/ubuntu-system-settings/rtm- lp1329702_battery_charging_status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1416096 Title: expose battery charging state on the bus Status in the base for Ubuntu mobile products: Confirmed Status in indicator-power package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Status in indicator-power package in Ubuntu RTM: Confirmed Status in ubuntu-system-settings package in Ubuntu RTM: In Progress Bug description: Requested by kenvandine in #ubuntu-touch on freenode for u-s-s to show the right battery status. He needs it for bug 1329702. Since that's a proprietary bug that can't affect multiple projects, this is a separately filed ticket. Since this for the qml in u-s-s, this should be a GAction state similar to how auto-brightness' state is exposed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351299] Re: [Location Indicator Menu] GPS switch should be turned off when "Location detection" is off
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-system-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1351299 Title: [Location Indicator Menu] GPS switch should be turned off when "Location detection" is off Status in Ubuntu UX bugs: Triaged Status in indicator-location package in Ubuntu: Incomplete Status in location-service package in Ubuntu: Confirmed Status in trust-store package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: After a conversation with tvoss, I understand that if I turn the "Location detection" switch off, effectively GPS will be turned off too. However, the two switches are independent: I can switch "Location detection" off and the "GPS" switch will stay on. This might be confusing for users: I'd expect both switches to go off when turning "Location detection" off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351299] Re: [Location Indicator Menu] GPS switch should be turned off when "Location detection" is off
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1351299 Title: [Location Indicator Menu] GPS switch should be turned off when "Location detection" is off Status in Ubuntu UX bugs: Triaged Status in indicator-location package in Ubuntu: Incomplete Status in location-service package in Ubuntu: Confirmed Status in trust-store package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: After a conversation with tvoss, I understand that if I turn the "Location detection" switch off, effectively GPS will be turned off too. However, the two switches are independent: I can switch "Location detection" off and the "GPS" switch will stay on. This might be confusing for users: I'd expect both switches to go off when turning "Location detection" off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351299] Re: [Location Indicator Menu] GPS switch should be turned off when "Location detection" is off
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: trust-store (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1351299 Title: [Location Indicator Menu] GPS switch should be turned off when "Location detection" is off Status in Ubuntu UX bugs: Triaged Status in indicator-location package in Ubuntu: Incomplete Status in location-service package in Ubuntu: Confirmed Status in trust-store package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: After a conversation with tvoss, I understand that if I turn the "Location detection" switch off, effectively GPS will be turned off too. However, the two switches are independent: I can switch "Location detection" off and the "GPS" switch will stay on. This might be confusing for users: I'd expect both switches to go off when turning "Location detection" off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351299/+subscriptions -- Mailing list: https://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] [Aims] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Hi Do you have this exactly? 0 root@muizenberg:~#ls -l /sbin/unix_chkpwd -rwsr-sr-x 1 root shadow 35536 Feb 1 2014 /sbin/unix_chkpwd I am uising libpam-ldap*d* and it works. Note the d. Regards, Jan On 30 January 2015 at 19:05, Vincent Jestin wrote: > Hello, > > Same problem here after doing an upgrade from 12.04 to 14.04. > > On the affected machine, some users (basically admins) have both unix > accounts and LDAP accounts. > > Users with both accounts can log in with unix or ldap password. However, > when the desktop is locked, the only way to unlock is to use a unix > password. > > I've tried unix_chkpwd suid workaround (no success) and checked > /etc/shadow file permissions (was ok). > > I'm using libpam-ldap. > > -- > You received this bug notification because you are a member of AIMS, > which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1314095 > > Title: > Unity Lockscreen in 14.04 can't unlock when using LDAP account > > Status in Unity: > Incomplete > Status in unity package in Ubuntu: > Incomplete > > Bug description: > My setup is: > > Ubuntu 14.04 LTS, > ldap accounts, > krb5 authentication, > Lightdm, > Unity session > > ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent > passwd and getent shadow works fine. > I am able to login in console without any problems. > I was able to login in lightdm. > Then I used the lock screen. > I could not disable the lock screen using my password. > I rebooted my computer. > > Now: > After logging in through lightdm, the unity lockscreen locks the screen > immediately and I can not disable it using my password. > > From my short inspection of auth.log and unix_chkpwd sources it seems, > that unix_chkpwd works fine when called from lightdm and fails to get > user info when called from unity lockscreen. > > > lsb_release -rd > Description: Ubuntu 14.04 LTS > Release: 14.04 > > apt-cache policy unity lightdm libpam-modules > unity: > Installed: 7.2.0+14.04.20140416-0ubuntu1 > Candidate: 7.2.0+14.04.20140416-0ubuntu1 > Version table: >*** 7.2.0+14.04.20140416-0ubuntu1 0 > 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages > 100 /var/lib/dpkg/status > lightdm: > Installed: 1.10.0-0ubuntu3 > Candidate: 1.10.0-0ubuntu3 > Version table: >*** 1.10.0-0ubuntu3 0 > 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages > 100 /var/lib/dpkg/status > libpam-modules: > Installed: 1.1.8-1ubuntu2 > Candidate: 1.1.8-1ubuntu2 > Version table: >*** 1.1.8-1ubuntu2 0 > 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages > 100 /var/lib/dpkg/status > > Contents of /var/log/auth.log: > > Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "user" > Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): > authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= > user=user > Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user > authenticated as user@NETWORK > Apr 29 06:49:32 localhost lightdm[15604]: > pam_unix(lightdm-greeter:session): session closed for user lightdm > Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown > Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for > user (user) > Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication > failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user > Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user > authenticated as user@NETWORK > Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info > (user) > Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info > (user) > Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): > requirement "user ingroup nopasswdlogin" not met by user "user" > > cat /etc/pam.d/common-auth > account requiredpam_unix.so > authrequiredpam_group.so > auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure > auth [success=1 default=ignore] pam_krb5.so try_first_pass > minimum_uid=200 > authrequisite pam_deny.so > authrequiredpam_permit.so > > authoptionalpam_afs_session.so minimum_uid=200 > authoptionalpam_ecryptfs.so unwrap > authoptionalpam_cap.so > > cat /etc/pam.d/common-account > account requiredpam_unix.so > > cat /etc/pam.d/lightdm > authrequisite pam_nologin.so > authsufficient pam_succeed_if.so user ingroup nopasswdlogin > @include common-auth > authoptionalpam_gnome_keyring.so > @include common-account > session [success=ok ignore=ignore module_unknown=ignore default=bad] > pam_selinux.so close > authoptionalpam_group
[Touch-packages] [Bug 1390011] Re: using new gtk, gedit's fileselector "encoding combo" has no preselected value
** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Triaged => Fix Committed ** Package changed: ubuntu => gedit (Ubuntu) ** Bug watch added: GNOME Bug Tracker #733422 https://bugzilla.gnome.org/show_bug.cgi?id=733422 ** Also affects: gedit via https://bugzilla.gnome.org/show_bug.cgi?id=733422 Importance: Unknown Status: Unknown -- 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/1390011 Title: using new gtk, gedit's fileselector "encoding combo" has no preselected value Status in Light-Weight Text Editor for Gnome: Unknown Status in gedit package in Ubuntu: Fix Committed Bug description: Trying to the new gtk candidate version for vivid, gedit fileselectors (in open/save dialogs) have an encoding combobox. That one displays a selected value by default using gtk 3.12, but not with the update To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1390011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416520] [NEW] vivid: Sound indicator pops up on initial boot after a flash
Public bug reported: STEPS: 1. Flash vivid 84+ onto you mako/manta/flo 2. When the welcome wizard start run though it 3. At some point in the wizard or just after the volume osd with popup EXPECTED: I don't expect to the the indicator popup randomly ACTUAL: At some point in the boot process post flash the sound indicator osd pops up. ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1416520 Title: vivid: Sound indicator pops up on initial boot after a flash Status in indicator-sound package in Ubuntu: New Bug description: STEPS: 1. Flash vivid 84+ onto you mako/manta/flo 2. When the welcome wizard start run though it 3. At some point in the wizard or just after the volume osd with popup EXPECTED: I don't expect to the the indicator popup randomly ACTUAL: At some point in the boot process post flash the sound indicator osd pops up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1416520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1168742]
Fixed in upstream git, will be in 219: http://cgit.freedesktop.org/systemd/systemd/commit/?id=06e9783e http://cgit.freedesktop.org/systemd/systemd/commit/?id=3b48ce4ec -- 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/1168742 Title: [udev] Disks are not unmounted when physical eject button is used Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Bug description: In 13.04, disks (DVDs, CDS) are not unmounted when ejected via the hardware button on the drive. After ejecting disks via the hardware button, an entry for the disk still shows up in the file manager, and shows when I run df. If I do a soft eject (ie from the right click menu from the icon on the launcher), however, everything works properly. Just as a note, as per https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions, I attempted to report this using ubuntu-bug storage, however there is not an option dealing with unmounting devices, and clicking other tells you that you should run ubuntu-bug again with a specific package name. In an attempt to get this to a semi-relevant audience, I ended up just saying that a disk wasn't auto-mounted, clicking through the next few popups, and ended up here. If this isn't the right place to report this bug, I apologize. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-17-generic 3.8.0-17.27 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 1590 F pulseaudio /dev/snd/controlC0: chris 1590 F pulseaudio Date: Sat Apr 13 12:54:33 2013 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=bd2c881c-7bf8-4996-8b05-7efbd9852333 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2013-03-26 (18 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130325) MachineType: ASUSTeK COMPUTER INC. G55VW MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic root=UUID=f44b6481-8a06-4cf1-a494-0e4c233720c8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-17-generic N/A linux-backports-modules-3.8.0-17-generic N/A linux-firmware1.105 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 12:54:42.343: The udisks-daemon is running (name-owner :1.39). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G55VW.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G55VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G55VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1168742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
