[Touch-packages] [Bug 1264311] Re: BCM43142 bluetooth adapter not finding any bluetooth devices
Okay, I got it to work, too now. Nevertheless, my bluetooth does not get initialized every time after a fresh reboot. Trying sudo modprobe btusb then gives: "Can't init device hci0: Connection timed out (110)". Running a Lenovo B590 on Ubuntu 13.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1264311 Title: BCM43142 bluetooth adapter not finding any bluetooth devices Status in “bluez” package in Ubuntu: Confirmed Bug description: On my officially Ubuntu-certified Lenovo B590 laptop the BCM43142 bluetooth adapter is not working. I have two further bluetooth devices placed closely to the laptop, non-paired and each being able to discover the other respectively. None of them is able to discover the laptop, nor does 'hcitool scan' on the laptop find any devices. It does not give any errors though. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluez 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Dec 26 15:34:08 2013 InstallationDate: Installed on 2013-12-25 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: LENOVO 37613EG MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=UUID=c379c17a-9869-47a8-b9b3-83be4e302040 ro acpi_backlight=vendor quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H9ET74WW(1.11) dmi.board.asset.tag: Not Available dmi.board.name: 37613EG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH9ET74WW(1.11):bd06/26/2013:svnLENOVO:pn37613EG:pvrLenovoB590:rvnLENOVO:rn37613EG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 37613EG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 1C:3E:84:E8:81:98 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1244 acl:0 sco:0 events:81 errors:0 TX bytes:2820 acl:0 sco:0 commands:77 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
Oh ok, then it has just been a (failed) desperate attempt. :) Thanks for the explanation. -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound in headphones jack after suspend/resume. But sound in headphones jack is OK after cold boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314787] Re: Memory leak
I have the same problem. I have a DELL XP with 8GB and a AMD Radeon 5700 XOrg will grow to take up around 5-6 GB every 24 hours. I have to kill Xorg with "sudo restart lightdm" daily. The issue only started after I upgraded from Ubuntu 13.10 to 14.04 Please help ! -- 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/1314787 Title: Memory leak Status in “xorg” package in Ubuntu: Confirmed Bug description: I upgraded my PC from Ubuntu 13.10 to 14.04 (released one). After upgrade I found the PC slows down soon even without apps running on it. When checking with system monitor I found all the physical memory was full and the swap file was in use (which never happened with 13.10). I restarted the PC and left it alone. After six hours memory consumption of xorg went from original 250MB to 1,3GB. I guess there is a memory leak in the process. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 NonfreeKernelModules: fglrx .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: Wed Apr 30 23:05:47 2014 DistUpgraded: 2014-04-26 21:44:20,660 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.11.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2291] InstallationDate: Installed on 2013-10-29 (183 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-20-generic root=UUID=a4de809d-e263-4318-8bf0-1bd1422076e3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-26 (4 days ago) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1105 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N78 SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.fglrx-installer: fglrx-installer N/A 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.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: Wed Apr 30 22:53:24 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open
[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
NO, not all HDA codec allow you to change Mic Jack into the headphone jack, usually the notebook have utilialized the volume controls of the 4 or 6 channels codec and don't have any spare dac or amp for the extra headphone http://voices.canonical.com/david.henningsson/2011/11/29/turn-your-mic-jack-into-a-headphone-jack/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound in headphones jack after suspend/resume. But sound in headphones jack is OK after cold boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351815] Re: StartTransientUnit signature has changed in systemd 214
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1351815 Title: StartTransientUnit signature has changed in systemd 214 Status in “systemd-shim” package in Ubuntu: New Bug description: This will be required when systemd gets updated to 214 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 6-4bzr1 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 3 14:05:50 2014 InstallationDate: Installed on 2012-09-23 (679 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348039] Re: shim does not implement 'Subscribe' method called by logind
This error is now fatal in systemd214. https://bitbucket.org/unit193/systemd/commits/c2310b408fc0cbdccb2253d6e3c2f8bd3f6490e9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1348039 Title: shim does not implement 'Subscribe' method called by logind Status in “systemd-shim” package in Ubuntu: Triaged Bug description: Get that error logged at the end of the dmesg file. That error seems to have no sad effect on the system: [ 30.793181] systemd-logind[1006]: Failed to enable subscription: No such method 'Subscribe' ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-6ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.4-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Thu Jul 24 07:25:46 2014 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1348039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351815] [NEW] StartTransientUnit signature has changed in systemd 214
Public bug reported: This will be required when systemd gets updated to 214 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 6-4bzr1 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 3 14:05:50 2014 InstallationDate: Installed on 2012-09-23 (679 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1351815 Title: StartTransientUnit signature has changed in systemd 214 Status in “systemd-shim” package in Ubuntu: New Bug description: This will be required when systemd gets updated to 214 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 6-4bzr1 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 3 14:05:50 2014 InstallationDate: Installed on 2012-09-23 (679 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351815] Re: StartTransientUnit signature has changed in systemd 214
** Patch added: "StartTransientUnit.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+attachment/4168494/+files/StartTransientUnit.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1351815 Title: StartTransientUnit signature has changed in systemd 214 Status in “systemd-shim” package in Ubuntu: New Bug description: This will be required when systemd gets updated to 214 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 6-4bzr1 ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 Uname: Linux 3.16.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 3 14:05:50 2014 InstallationDate: Installed on 2012-09-23 (679 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: systemd-shim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1351815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351814] [NEW] manager crash: GLib-GObject-CRITICAL (ubutu 13)
Public bug reported: When I insert my modem (huawei e153u) the aplication is closed: The error on console: Module applicable: Modem Manager <= 0.6.0/Wader (modmm_mm06.so) Module applicable: pppd >= 2.4.5 (modcm_pppd245.so) Connection manager: pppd >= 2.4.5 Modem manager: Modem Manager <= 0.6.0/Wader Device: huawei, E153, 11.609.18.00.279 [3] [44af59d16429bca0c4a77be00627e2d3] (modem-manager-gui:8350): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Device successfully opened Segmentation fault at address: 0x8 Stack trace: 1. /lib/x86_64-linux-gnu/libc.so.6(+0xb8b5d) [0x7f597f77db5d] 2. /lib/x86_64-linux-gnu/libc.so.6(+0xb8b5d) [0x7f597f77db5d] 3. /lib/x86_64-linux-gnu/libc.so.6(strftime_l+0x16) [0x7f597f77f9a6] 4. modem-manager-gui() [0x41b9e7] 5. modem-manager-gui() [0x41f372] 6. modem-manager-gui() [0x41f4f3] 7. modem-manager-gui() [0x423abd] 8. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x138) [0x7f59803c5188] 9. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x21b1d) [0x7f59803d6b1d] I use ubuntu 13.10 thanks and sorry for my english. PD: the first time it works fine, but I restart the computer and not work more :/. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1351814 Title: manager crash: GLib-GObject-CRITICAL (ubutu 13) Status in “modemmanager” package in Ubuntu: New Bug description: When I insert my modem (huawei e153u) the aplication is closed: The error on console: Module applicable: Modem Manager <= 0.6.0/Wader (modmm_mm06.so) Module applicable: pppd >= 2.4.5 (modcm_pppd245.so) Connection manager: pppd >= 2.4.5 Modem manager: Modem Manager <= 0.6.0/Wader Device: huawei, E153, 11.609.18.00.279 [3] [44af59d16429bca0c4a77be00627e2d3] (modem-manager-gui:8350): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Device successfully opened Segmentation fault at address: 0x8 Stack trace: 1. /lib/x86_64-linux-gnu/libc.so.6(+0xb8b5d) [0x7f597f77db5d] 2. /lib/x86_64-linux-gnu/libc.so.6(+0xb8b5d) [0x7f597f77db5d] 3. /lib/x86_64-linux-gnu/libc.so.6(strftime_l+0x16) [0x7f597f77f9a6] 4. modem-manager-gui() [0x41b9e7] 5. modem-manager-gui() [0x41f372] 6. modem-manager-gui() [0x41f4f3] 7. modem-manager-gui() [0x423abd] 8. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x138) [0x7f59803c5188] 9. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x21b1d) [0x7f59803d6b1d] I use ubuntu 13.10 thanks and sorry for my english. PD: the first time it works fine, but I restart the computer and not work more :/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1351814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
Thanks a ton for your efforts guys. I really hope you can figure out what is wrong (wish I could actively help but I can only test). In the meanwhile I've been playing around with a tool that remaps the various jacks (e.g. mic can become line-out). You can find it here: https://launchpad.net/~diwic/+archive/ubuntu/hda, it is now part of the package alsa-tools-gui. I wasn't able to get the mic jack to work as line-out/headphones but I managed to "crash" the speakers by trying to override them. I don't know anything about codecs nor circuits but maybe you can find a workaround using this tool? Again, thanks for your help. -- 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/1313904 Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: No sound in headphones jack after suspend/resume. But sound in headphones jack is OK after cold boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.15.0-031500rc2-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:20:59 2014 InstallationDate: Installed on 2014-04-26 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Вбудоване аудіо - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mik2139 F pulseaudio /dev/snd/controlC1: mik2139 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/11/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd02/11/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-28T23:13:10.065027 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1313904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351610] Re: LightDM looses focus
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- 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/1351610 Title: LightDM looses focus Status in “unity” package in Ubuntu: New Bug description: Sometimes after I wake up from suspend, LightDM seems to lost focus to a window in the desktop. I have a blinking cursor in the LightDM screen, and if I start typing anything the cursor doesn't move, and the only way to bypass this is wait the screen to turn off and on again (here I can type the password). This also happens when locking the screen. Description: Ubuntu 14.04.1 LTS Release: 14.04 Lightdm version: 1.10.1-0ubuntu1 How to reproduce: * Open a window and click on a text box (ex: login form in some web page in a browser). * Lock the screen * Try to type your password to unlock it: the cursor blinks but doesn't move at all; * Wait for the screen to turn off, do something to wake up the screen and login; * Whatever you typed will be on the text input of the window you had focus (in this example: the login form of the web page) What was supposed to happen: * After locking the screen or waking from suspend, I expected that typing my password would unlock the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349789] Re: clang armhf in trusty simply doesn't work
Good news on this, though it took a day of head scratching to figure it out. It turns out that ARM clang 3.3 and earlier implements C++ exceptions using the inefficient SJLJ exception ABI - you know, the one that calls setjmp all the time for every place an unwind might happen. Anyway, they finally got round to implementing the ARM EHABI exception ABI which is zero runtime cost and they went ahead and turned it on by default in 3.4, or at least it is being turned on by default in the Debian/Ubuntu binaries as well as the LLVM binaries. Unfortunately, it was very broken indeed. It produces ARM binaries which simply cannot catch non-trivial C++ exceptions, though otherwise work fine. This caused Boost.Thread when interrupting a thread wait to enter an infinite loop at described above, indeed if you EVER catch a type with RTTI it infinite loops. Fortunately, Chromium realised this shortly after the 3.4 release, and they've been hard at work making a EHABI implementation which actually works for 3.5. I just finished compiling 3.5 from trunk and I can confirm that all Boost.AFIO unit test pass swimmingly with it for armhf. You can read more about the 3.5 ARM exception handling improvements at http://llvm.org/docs/ReleaseNotes.html#changes-to-the-arm-backend. Can I recommend you upcall this to Debian as well and recommend that they mark clang 3.4 as broken on ARM? Either that or have them patched to disable EHABI exception handling? Niall -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1349789 Title: clang armhf in trusty simply doesn't work Status in “llvm-toolchain-3.4” package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 14.04 on armhf. clang is from the standard repo: root@tegra-ubuntu:~# apt-cache show clang Package: clang Priority: optional Section: universe/devel Installed-Size: 27 Maintainer: Ubuntu Developers Original-Maintainer: LLVM Packaging Team Architecture: armhf Source: llvm-defaults (0.21ubuntu1) Version: 1:3.4-0ubuntu1 Replaces: clang (<< 3.2-1~exp2) Depends: clang-3.4 (>= 3.4~rc3-1~) Filename: pool/universe/l/llvm-defaults/clang_3.4-0ubuntu1_armhf.deb Size: 2478 MD5sum: eadb3f7c344e364480bdf7fdd0f698ab SHA1: ec4d0bfcad42bf536ee8d9257f8930dd32e1a261 SHA256: f6d9a8fbfc06d93cd4c1a2437114454cc1eec805a635efc490a7e1e6eec2b3de Description-en: C, C++ and Objective-C compiler (LLVM based) Clang project is a C, C++, Objective C and Objective C++ front-end for the LLVM compiler. Its goal is to offer a replacement to the GNU Compiler Collection (GCC). . Clang implements all of the ISO C++ 1998 and 2001 standards and also provides a partial support of C++1y. . This is a dependency package providing the default clang compiler. Description-md5: ea1f164ac255f39c6ec78685f71ef19b Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Anyway, it does not produce working output. Here are some examples: https://ci.nedprod.com/view/Boost.AFIO/job/Boost.AFIO%20Build%20POSIX_ARM_clang%203.4/9/consoleFull This log shows how clang has the wrong default target CPU, so it outputs unsupported ARM instructions (see the end after the warnings spew). If I force the target cpu to a cortex-a15 it now at least compiles and links and starts to run unit tests: https://ci.nedprod.com/view/Boost.AFIO/job/Boost.AFIO%20Test%20POSIX_ARM_clang%203.4/7/consoleFull ... but hangs in the first unit test, and is timed out. Before you think it the unit tests, here is the exact same thing for GCC 4.8: https://ci.nedprod.com/view/Boost.AFIO/job/Boost.AFIO%20Test%20POSIX_ARM_GCC%204.8/7/console The unit tests all run and pass as expected. Everything also works fine on x86 and x64 with clang 3.4 on Ubuntu 14.04, this appears to be an armhf misconfiguration. Niall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1349789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351641] Re: Launcher icon title does not disappear automatically
** Tags added: utopic -- 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/1351641 Title: Launcher icon title does not disappear automatically Status in “unity” package in Ubuntu: Confirmed Bug description: When you hover over an icon in the launcher bar with the cursor, a text field with the title of the application pops up. Usually this disappears as soon as you move the cursor away from the icon. However, it occasionally happens that the title does not disappear, and stays on screen even though the launcher bar is hidden again (I have auto- hide turned on). If that happens, you can get the title to disappear as it should by hovering the mouse over the same icon again and then moving it away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Sat Aug 2 18:33:50 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-27-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-29-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-30-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2014-04-23 (101 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20245 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e9acf7a8-4d74-4222-9079-5ec04553488a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7BCN36WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G500s dmi.modalias: dmi:bvnLENOVO:bvr7BCN36WW(V2.02):bd08/28/2013:svnLENOVO:pn20245:pvrLenovoG500s:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500s: dmi.product.name: 20245 dmi.product.version: Lenovo G500s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 2 17:53:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18002 vendor SDC xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347147] Re: krb5 database operations enter infinite loop
** Changed in: krb5 (Ubuntu) Importance: Undecided => High ** Changed in: krb5 (Ubuntu Trusty) Importance: Undecided => High ** Changed in: krb5 (Ubuntu Trusty) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1347147 Title: krb5 database operations enter infinite loop Status in The GNU Compiler Collection: Unknown Status in Network Authentication System: Unknown Status in “gcc-4.8” package in Ubuntu: Fix Released Status in “gcc-4.9” package in Ubuntu: Fix Released Status in “krb5” package in Ubuntu: Triaged Status in “gcc-4.8” source package in Trusty: New Status in “krb5” source package in Trusty: Triaged Bug description: [Impact] On krb5 KDC databases with more than a few hundred principals, operations can enter an infinite loop in the database library. This affects both read and write operations. If operators are fortunate, they will encounter this bug while testing a migration. If they are not so fortunate, they will encounter this bug in a production KDC when the number of principals crosses the threshold where this bug manifests, resulting in a service outage and possible database corruption. Probably the only way to restore service in that situation is to install a patched KDC or to downgrade to an unaffected version. Both Trusty and Utopic amd64 have been verified to have this issue. One concrete reported example is an invocation of kdb5_util load (as part of a slave KDC propagation) spinning: http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html Additional failure modes are likely A branch is linked including the upstream work around for this bug, along with two other patches to bugs already nominated for trusty applied to the krb5 in trusty. For utopic, the simplest fix is to rebuild krb5 with the compiler currently in utopic. An alternative is to request that the Debian maintainers (both monitoring this bug for such a request) upload the upstream work around to Debian and sync that. You could do an ubuntu- specific upload but it seems undesirable to introduce a change between Ubuntu and Debian when all the right parties are happy to avoid it. The upstream patch works around a compiler optimizer bug in the gcc-4.8 series, which incorrectly deduces that a strict aliasing violation has occurred and miscompiles part of the bundled libdb2 library that the KDC database back end depends upon. The miscompilation causes a data structure to contain an inappropriate cycle, which leads to an infinite loop when the structure is traversed. [Test Case] apt-get install krb5-kdc krb5-admin-server kdb5_util -W -r T create -s awk 'BEGIN{ for (i = 0; i < 1024; i++) { printf("ank -randkey a%06d\n", i) } }' /dev/null | kadmin.local -r T (Enter any password for the master key when requested.) On platforms with this issue, kadmin.local spins consuming 100% CPU after a few hundred principals have been created. (This is "a000762" on two examples.) To clean up, rm /etc/krb5kdc/principal* or krb5kdc -r T destroy but the latter can possibly enter the same infinite loop. [Regression Potential] Negligible. It is theoretically possible that our upstream workaround, which involves using TAILQ macros instead of CIRCLEQ macros in the bundled libdb2 that backs the KDC database, will have some as-yet undiscovered bugs or compiler interactions with consequences worse than this current issue. I think this is rather unlikely. The patched libdb2 passes both the extensive libdb2 test suite and the rest of the krb5 test suite. Prior to patching, compiling krb5 with an affected gcc would cause the krb5 test suite to stall when it reached the libdb2 test suite. (The test suite stall is how we became aware of the gcc optimizer bug.) The BSD TAILQ macros are generally considered to be safer than the CIRCLEQ macros, and the various open-source BSD derivatives have made the corresponding change to their libdb sources years ago, with no reported ill effects that I can see. Original report from Ben Kaduk: == In some conditions, propagating a kerberos database to a slave KDC server can stall. This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros, apparently due to overzealous strict aliasing deductions. One case of this stall is reported at http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html (and the rest of the thread), and there is an entry in the upstream bugtracker at http://krbdev.mit.edu/rt/Ticket/Display.html?id=7860 . gcc 4.9 (as used in Debian unstable at present) is not believed to induce this problem. Upstream has patched their code to use the TAILQ family of macros instead, as a workaround, but that workaround has not yet
[Touch-packages] [Bug 1351758] [NEW] Unmounted devices stay on launcher with slugged icons
Public bug reported: When i unmount flash drive or CD - sometimes unmounted device icon stays on launcher, a little minimized. Looks like animation stopped playing. See the screenshot ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Aug 3 03:34:33 2014 InstallationDate: Installed on 2014-01-14 (200 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (106 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: "Снимок экрана от 2014-08-03 03:34:03.png" https://bugs.launchpad.net/bugs/1351758/+attachment/4168407/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202014-08-03%2003%3A34%3A03.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1351758 Title: Unmounted devices stay on launcher with slugged icons Status in “unity” package in Ubuntu: New Bug description: When i unmount flash drive or CD - sometimes unmounted device icon stays on launcher, a little minimized. Looks like animation stopped playing. See the screenshot ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Aug 3 03:34:33 2014 InstallationDate: Installed on 2014-01-14 (200 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
Though, the Unity code doesn't seem to use HSplitter or VSplitter. Also, it doesn't call QueueRelayout on any InputArea objects, which seems to be the only other way for an InputArea object to be put on the layout queue. Btw the "parent object of an object of type InputArea is a Layout object" comment at Area.cpp:603 is indeed wrong, since UnityWindowView::GetBoundingArea() has a counterexample. -- 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/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Nux: New Status in Unity: Confirmed Status in “nux” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, this is basically the same bug as https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing this bug on trusty, with the latest Unity version (unity 7.2.1+14.04.20140513-0ubuntu2). I already mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::list >&, unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::list >&, unsigned int, CompRegion const&) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::list >&, unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7f007879b5ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7f007879ab4d in Com
[Touch-packages] [Bug 1342923] Re: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()
pop from apport again, this time when launching Opera-Develeper 24.0 Web browser -C -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1342923 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() Status in Meta-tracker: Fix Released Status in Ubuntu GNOME: Triaged Status in “tracker” package in Ubuntu: Triaged Bug description: i ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: tracker 1.0.2-1ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 3.13.0-32.56-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 16 21:39:09 2014 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2014-07-16 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x7f02dd2c9cb3 <_IO_vfprintf_internal+7443>: repnz scas %es:(%rdi),%al PC (0x7f02dd2c9cb3) ok source "%es:(%rdi)" (0xc0023630) not located in a known VMA region (needed readable region)! destination "%al" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: tracker StacktraceTop: _IO_vfprintf_internal (s=s@entry=0x7f02d37fd600, format=, format@entry=0x7f02de5f5da0 "Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s')", ap=ap@entry=0x7f02d37fd7a8) at vfprintf.c:1661 __GI___vasprintf_chk (result_ptr=0x7f02d37fd758, flags=1, format=0x7f02de5f5da0 "Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s')", args=0x7f02d37fd7a8) at vasprintf_chk.c:66 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_error_new_valist () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() 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/tracker/+bug/1342923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351743] Re: not ready dm node is causing no swap
... and when it's not ready ** Attachment added: "no-swap.log" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1351743/+attachment/4168394/+files/no-swap.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1351743 Title: not ready dm node is causing no swap Status in “mountall” package in Ubuntu: New Bug description: ubuntu 14.04 mountall 2.53 Sometimes mountall is not mounting /dev/mapper/cryptswap1 because the /dev/dm-0 node is not being ready. Mountall debug log when it's ready: - try_mount: /dev/mapper/cryptswap1 waiting for device try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/sda3 0bc51a6d-e14e-4586-8313-4d2ec5b54201 (null) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/dm-0 ebef4c79-048a-45b8-a18f-2fbeaa6ac738 (null) try_udev_device: /dev/mapper/cryptswap1 by link /dev/mapper/cryptswap1 run_fsck: /dev/mapper/cryptswap1: no check required mounting event sent for swap /dev/mapper/cryptswap1 mounting event handled for swap /dev/mapper/cryptswap1 activating /dev/mapper/cryptswap1 spawn: swapon /dev/mapper/cryptswap1 spawn: swapon /dev/mapper/cryptswap1 [1049] swapon /dev/mapper/cryptswap1 [1049] exited normally mounted: /dev/mapper/cryptswap1 fsck_update: updating check priorities mounted event handled for swap /dev/mapper/cryptswap1 swap finished Block device attributtes when the swap is on: -- (sudo blkid /dev/mapper/cryptswap1);(sudo blkid /dev/dm-0) /dev/mapper/cryptswap1: UUID="ebef4c79-048a-45b8-a18f-2fbeaa6ac738" TYPE="swap" /dev/dm-0: UUID="ebef4c79-048a-45b8-a18f-2fbeaa6ac738" TYPE="swap" Mountall debug log when it's not ready: --- try_mount: /dev/mapper/cryptswap1 waiting for device try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/sda3 0bc51a6d-e14e-4586-8313-4d2ec5b54201 (null) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_mount: /dev/mapper/cryptswap1 waiting for device try_mount: /dev/mapper/cryptswap1 waiting for device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1351743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351743] [NEW] not ready dm node is causing no swap
Public bug reported: ubuntu 14.04 mountall 2.53 Sometimes mountall is not mounting /dev/mapper/cryptswap1 because the /dev/dm-0 node is not being ready. Mountall debug log when it's ready: - try_mount: /dev/mapper/cryptswap1 waiting for device try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/sda3 0bc51a6d-e14e-4586-8313-4d2ec5b54201 (null) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/dm-0 ebef4c79-048a-45b8-a18f-2fbeaa6ac738 (null) try_udev_device: /dev/mapper/cryptswap1 by link /dev/mapper/cryptswap1 run_fsck: /dev/mapper/cryptswap1: no check required mounting event sent for swap /dev/mapper/cryptswap1 mounting event handled for swap /dev/mapper/cryptswap1 activating /dev/mapper/cryptswap1 spawn: swapon /dev/mapper/cryptswap1 spawn: swapon /dev/mapper/cryptswap1 [1049] swapon /dev/mapper/cryptswap1 [1049] exited normally mounted: /dev/mapper/cryptswap1 fsck_update: updating check priorities mounted event handled for swap /dev/mapper/cryptswap1 swap finished Block device attributtes when the swap is on: -- (sudo blkid /dev/mapper/cryptswap1);(sudo blkid /dev/dm-0) /dev/mapper/cryptswap1: UUID="ebef4c79-048a-45b8-a18f-2fbeaa6ac738" TYPE="swap" /dev/dm-0: UUID="ebef4c79-048a-45b8-a18f-2fbeaa6ac738" TYPE="swap" Mountall debug log when it's not ready: --- try_mount: /dev/mapper/cryptswap1 waiting for device try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/sda3 0bc51a6d-e14e-4586-8313-4d2ec5b54201 (null) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_mount: /dev/mapper/cryptswap1 waiting for device try_mount: /dev/mapper/cryptswap1 waiting for device ** Affects: mountall (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1351743 Title: not ready dm node is causing no swap Status in “mountall” package in Ubuntu: New Bug description: ubuntu 14.04 mountall 2.53 Sometimes mountall is not mounting /dev/mapper/cryptswap1 because the /dev/dm-0 node is not being ready. Mountall debug log when it's ready: - try_mount: /dev/mapper/cryptswap1 waiting for device try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/sda3 0bc51a6d-e14e-4586-8313-4d2ec5b54201 (null) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/dm-0 ebef4c79-048a-45b8-a18f-2fbeaa6ac738 (null) try_udev_device: /dev/mapper/cryptswap1 by link /dev/mapper/cryptswap1 run_fsck: /dev/mapper/cryptswap1: no check required mounting event sent for swap /dev/mapper/cryptswap1 mounting event handled for swap /dev/mapper/cryptswap1 activating /dev/mapper/cryptswap1 spawn: swapon /dev/mapper/cryptswap1 spawn: swapon /dev/mapper/cryptswap1 [1049] swapon /dev/mapper/cryptswap1 [1049] exited normally mounted: /dev/mapper/cryptswap1 fsck_update: updating check priorities mounted event handled for swap /dev/mapper/cryptswap1 swap finished Block device attributtes when the swap is on: -- (sudo blkid /dev/mapper/cryptswap1);(sudo blkid /dev/dm-0) /dev/mapper/cryptswap1: UUID="ebef4c79-048a-45b8-a18f-2fbeaa6ac738" TYPE="swap" /dev/dm-0: UUID="ebef4c79-048a-45b8-a18f-2fbeaa6ac738" TYPE="swap" Mountall debug log when it's not ready: --- try_mount: /dev/mapper/cryptswap1 waiting for device try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/sda3 0bc51a6d-e14e-4586-8313-4d2ec5b54201 (null) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_mount: /dev/mapper/cryptswap1 waiting for device try_mount: /dev/mapper/cryptswap1 waiting for device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1351743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351743] Re: not ready dm node is causing no swap
mountall.log when it's ready ** Attachment added: "swap-ok.log" https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1351743/+attachment/4168393/+files/swap-ok.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/1351743 Title: not ready dm node is causing no swap Status in “mountall” package in Ubuntu: New Bug description: ubuntu 14.04 mountall 2.53 Sometimes mountall is not mounting /dev/mapper/cryptswap1 because the /dev/dm-0 node is not being ready. Mountall debug log when it's ready: - try_mount: /dev/mapper/cryptswap1 waiting for device try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/sda3 0bc51a6d-e14e-4586-8313-4d2ec5b54201 (null) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/dm-0 ebef4c79-048a-45b8-a18f-2fbeaa6ac738 (null) try_udev_device: /dev/mapper/cryptswap1 by link /dev/mapper/cryptswap1 run_fsck: /dev/mapper/cryptswap1: no check required mounting event sent for swap /dev/mapper/cryptswap1 mounting event handled for swap /dev/mapper/cryptswap1 activating /dev/mapper/cryptswap1 spawn: swapon /dev/mapper/cryptswap1 spawn: swapon /dev/mapper/cryptswap1 [1049] swapon /dev/mapper/cryptswap1 [1049] exited normally mounted: /dev/mapper/cryptswap1 fsck_update: updating check priorities mounted event handled for swap /dev/mapper/cryptswap1 swap finished Block device attributtes when the swap is on: -- (sudo blkid /dev/mapper/cryptswap1);(sudo blkid /dev/dm-0) /dev/mapper/cryptswap1: UUID="ebef4c79-048a-45b8-a18f-2fbeaa6ac738" TYPE="swap" /dev/dm-0: UUID="ebef4c79-048a-45b8-a18f-2fbeaa6ac738" TYPE="swap" Mountall debug log when it's not ready: --- try_mount: /dev/mapper/cryptswap1 waiting for device try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: block /dev/sda3 0bc51a6d-e14e-4586-8313-4d2ec5b54201 (null) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_udev_device: ignored /dev/dm-0 (not yet ready?) try_mount: /dev/mapper/cryptswap1 waiting for device try_mount: /dev/mapper/cryptswap1 waiting for device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1351743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313813] Re: amixer 'mute toggle shortcut' problem (can mute but not unmute)
On further investigation. Looks similar to Bug #1026331 (duplicate of #878986). Which, according to the comments on the latter is a Pulseaudio issue. Fixed (or rather triaged) by using amixer -D pulse set Master toggle (which worked for me) or using pactl set-sink-mute 0 (which wouldn't recognise the sink name) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1313813 Title: amixer 'mute toggle shortcut' problem (can mute but not unmute) Status in “alsa-utils” package in Ubuntu: Confirmed Bug description: Openbox shortcut configuration file on ~/.config/openbox/lubuntu- rc.xml triggers to the following command to be executed: $ amixer -q sset Master toggle This problem is language related/dependent. This works fine on a pure english Lubuntu installation (toggle behavior). I installed Portuguese language package, on this very same machine, and now shortcut can mute, but I need to use the volume control on "tray" to unmute! I can solve the issue by running this command: $ amixer -q sset Master toggle && amixer -q sset Speaker unmute && amixer -q sset Headphone unmute A good workaround is edit ~/.config/openbox/lubuntu-rc.xml and set/reset this config.: amixer -q sset Master toggle amixer -q sset Speaker unmute amixer -q sset Headphone unmute ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-utils 1.0.27.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Apr 28 13:19:33 2014 InstallationDate: Installed on 2014-04-27 (1 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1313813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351640] Re: core file size: cannot modify limit: Operation not permitted
** Package changed: ubuntu => bash (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1351640 Title: core file size: cannot modify limit: Operation not permitted Status in “bash” package in Ubuntu: New Bug description: $ ulimit -c unlimited bash: ulimit: core file size: cannot modify limit: Operation not permitted $ grep core /etc/security/limits.conf #- core - limits the core file size (KB) * hardcoreunlimited * softcoreunlimited #roothardcore10 $ ulimit -S -c unlimited $ $ ulimit -a | grep core core file size (blocks, -c) 0 $ cat /proc/sys/kernel/core_pattern |/usr/share/apport/apport %p %s %c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1351640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351640] [NEW] core file size: cannot modify limit: Operation not permitted
You have been subscribed to a public bug: $ ulimit -c unlimited bash: ulimit: core file size: cannot modify limit: Operation not permitted $ grep core /etc/security/limits.conf #- core - limits the core file size (KB) * hardcoreunlimited * softcoreunlimited #roothardcore10 $ ulimit -S -c unlimited $ $ ulimit -a | grep core core file size (blocks, -c) 0 $ cat /proc/sys/kernel/core_pattern |/usr/share/apport/apport %p %s %c ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- core file size: cannot modify limit: Operation not permitted https://bugs.launchpad.net/bugs/1351640 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 708573] Re: USB headset mic not picked when I plug headset in
There is a Blog Message that can help: http://blog.ostermiller.org/ubuntu-usb-audio/ If it doesn't work and your login is more than 7 letters long, adjust the format-option in the line 62 from "ps axc -o user,command" to "ps axc -o user:XXX,command", where XXX is the length of your login+1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/708573 Title: USB headset mic not picked when I plug headset in Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio Whenever I plugged in my old audio jack headset, sound was immediately diverted from my speakers to the headset speakers, and the microphone was immediately available. When I plug in my new USB headset, I have to open Sound Preferences and switch both input to the headset. (Output is selected automatically, but I'm not sure if the first time it wasn't.) Aparrently this is a bug, not a configuration problem on my side. This may be a duplicate of or related to the following bugs - but none of these bugs described my specific issue (USB headset mic is not automatically picked): * https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/491055 * https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/443306 * https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/640328 * http://askubuntu.com/questions/21472/how-can-i-automatically-switch-to-usb-headset-when-plugged-in I'm using a Fujitsu-Siemens Amilo Pi laptop, Maverick and a Logitech H330 USB headset. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/708573/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
Yes, it's weird. Right now I suspect that the configuration file 65 -droid-sans-fonts.conf (attached), which the current fonts-droid package installs, is the root cause of this mess. That file seems to imply that if you install fonts-droid, you want Droid Sans fonts be used for all languages, while we are currently only interested in Droid Sans Fallback. In other words, it does not fit well with Ubuntu's default font configuration. I have modified the packages in my PPA a little. From the changelogs: fonts-android (1:4.3-3ubuntu1.1~ppa2) trusty; urgency=medium * Binary package split: - fonts-droid split into fonts-droid-cjk, which installs the Droid Sans Fallback font, and fonts-droid-general, which installs the rest. fonts-droid converted to a transitional dummy package which depends on fonts-droid-cjk. * debian/local/65-droid-sans-fonts.conf: - Recipes affecting Droid Sans Fallback dropped. language-selector (0.129.3~ppa2) trusty; urgency=low * fontconfig/69-language-selector-zh-??.conf: Reverse changes in version 0.129.2. * data/pkg_depends: Replace fonts-droid with fonts-droid-cjk. 65-droid-sans-fonts.conf is installed by the new fonts-droid-general package, but the Droid Sans Fallback related entries have been removed. I think that the packages in my PPA are now in a state which makes them uploadable to the archive. You may ask: Do we really need this package split? Wouldn't it be sufficient to modify (or drop) 65-droid-sans-fonts.conf? Honestly I'm not sure. To test that theory, you can simply install both fonts-droid- cjk and fonts-droid-general from my ppa. When I do so on my 14.04 desktop, it seems to work. At least for the moment... @Lukas: Can you please do the same, and let us know if Chinese is still rendered correctly in the qt apps? OTOH: Is it sensible to have to install all those fonts just to be able to use Droid Sans Fallback for Chinese? And what about the phone? @Iain: Your comments on all this would be appreciated. Apparently something needs to be done, also in trusty. ** Attachment added: "65-droid-sans-fonts.conf" https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+attachment/4168348/+files/65-droid-sans-fonts.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: New Status in “language-selector” package in Ubuntu: New Bug description: There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing CN" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai CN" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351238] Re: Install problem Brother-DCP 7065DN
~brian-murray Sorry I don't know how to remove the patch. I had attached that screenshot because it was a fix for me. and has been with two different machines. The problem is genuine and valid. I am not a member of the ~ubuntu-reviewers team. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1351238 Title: Install problem Brother-DCP 7065DN Status in “cups” package in Ubuntu: New Bug description: While working through the printer install process The printer was found and correctly identified as DCP-7065DN However the list of drivers offered did not include this and recommended driver DCP-7045N which did not work. Experimenting with choosing and finally choosing DCP-8065DN did work and the printer functions properly just blind luck. What I expected was to be offered the correct driver by name. This may be an error in naming or transcription; not sure. Very frustrating, to be sure and took a fair amount of work to find the right driver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 1 02:14:11 2014 InstallationDate: Installed on 2014-06-01 (60 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lpstat: device for Brother-DCP-7065DN: dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/ MachineType: LENOVO 10117 Papersize: letter PpdFiles: Brother-DCP-7065DN: Brother DCP8065DN for CUPS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=f4e792d4-f621-4310-bd0f-99182ad4edcd ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: I7KT31AUS dmi.board.vendor: LENOVO dmi.board.version: 31900058 STD dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr: dmi.product.name: 10117 dmi.product.version: Lenovo H535 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1351238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313813] Re: amixer 'mute toggle shortcut' problem (can mute but not unmute)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1313813 Title: amixer 'mute toggle shortcut' problem (can mute but not unmute) Status in “alsa-utils” package in Ubuntu: Confirmed Bug description: Openbox shortcut configuration file on ~/.config/openbox/lubuntu- rc.xml triggers to the following command to be executed: $ amixer -q sset Master toggle This problem is language related/dependent. This works fine on a pure english Lubuntu installation (toggle behavior). I installed Portuguese language package, on this very same machine, and now shortcut can mute, but I need to use the volume control on "tray" to unmute! I can solve the issue by running this command: $ amixer -q sset Master toggle && amixer -q sset Speaker unmute && amixer -q sset Headphone unmute A good workaround is edit ~/.config/openbox/lubuntu-rc.xml and set/reset this config.: amixer -q sset Master toggle amixer -q sset Speaker unmute amixer -q sset Headphone unmute ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-utils 1.0.27.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Apr 28 13:19:33 2014 InstallationDate: Installed on 2014-04-27 (1 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1313813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351464] Re: Ubuntu 14.10 pulse audio broken
There is no telling what caused the issue without the relevant log, so I'm closing the bug. If the issue occurs again or with a fresh install, please file a new bug against the pulseaudio package so that relevant logs are collected automatically. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1351464 Title: Ubuntu 14.10 pulse audio broken Status in “pulseaudio” package in Ubuntu: Invalid Bug description: In Ubuntu 14.10 Pulse audio options dont work at all and there's no Audio option in the top right of the screen any more. Not sure if that is already getting worked on and changed to something else but likely to happen to alpha versions of Ubuntu ^_^ but thought it was something that ya peeps would like to know just in case. the audio works but the options are not able to work in system settings plus if 1 was to search for pulse audio through the browser of programs it cant find it --- ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: darkangel 14561 F...m java /dev/snd/controlC0: darkangel 14561 F java /dev/snd/timer: darkangel 14561 f java CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=569c56dd-f25c-4a2d-bd00-ca52486d4cea InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140731) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: eMachines EL1360G NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=db39e416-41db-4526-8c10-85c1fcfc8fe2 ro quiet splash ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1351464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351464] Re: Ubuntu 14.10 pulse audio broken
Sorry may have to put this 1 on Hold for now just in case another person has the same issue in the future maybe. reason i cant bring any more infomation about this bug is cause of Fatal crash and could not repair the issue with bug: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1351480 when i had this bug my Ubuntu system was not bootable ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1351464 Title: Ubuntu 14.10 pulse audio broken Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10 Pulse audio options dont work at all and there's no Audio option in the top right of the screen any more. Not sure if that is already getting worked on and changed to something else but likely to happen to alpha versions of Ubuntu ^_^ but thought it was something that ya peeps would like to know just in case. the audio works but the options are not able to work in system settings plus if 1 was to search for pulse audio through the browser of programs it cant find it --- ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: darkangel 14561 F...m java /dev/snd/controlC0: darkangel 14561 F java /dev/snd/timer: darkangel 14561 f java CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=569c56dd-f25c-4a2d-bd00-ca52486d4cea InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140731) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: eMachines EL1360G NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=db39e416-41db-4526-8c10-85c1fcfc8fe2 ro quiet splash ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1351464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313813] Re: amixer 'mute toggle shortcut' problem (can mute but not unmute)
Also affects Ubuntu 14.04 Vanilla (running standalone Xmonad Window Manager, not Unity Desktop on Acer Aspire One D260). amixer -q sset Master toggle (or Master,0) also mutes Headphone and Speaker but does not unmute Headphone and Speaker when run again to unmute. Problem persists whether system plugged into speakers through headphone jack or not. Work-around also fixes problem for Xmonad (and also Herbstluftwm and other window managers) on vanilla Ubuntu. I have no additional languages installed (Native English speaker) , but ibus is managing keyboard (as default in 14.04). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1313813 Title: amixer 'mute toggle shortcut' problem (can mute but not unmute) Status in “alsa-utils” package in Ubuntu: New Bug description: Openbox shortcut configuration file on ~/.config/openbox/lubuntu- rc.xml triggers to the following command to be executed: $ amixer -q sset Master toggle This problem is language related/dependent. This works fine on a pure english Lubuntu installation (toggle behavior). I installed Portuguese language package, on this very same machine, and now shortcut can mute, but I need to use the volume control on "tray" to unmute! I can solve the issue by running this command: $ amixer -q sset Master toggle && amixer -q sset Speaker unmute && amixer -q sset Headphone unmute A good workaround is edit ~/.config/openbox/lubuntu-rc.xml and set/reset this config.: amixer -q sset Master toggle amixer -q sset Speaker unmute amixer -q sset Headphone unmute ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-utils 1.0.27.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Apr 28 13:19:33 2014 InstallationDate: Installed on 2014-04-27 (1 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1313813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349128] Re: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators)
A landing for the utopic release will likely happen on Monday. In the mean time you can download the packages from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-018/+packages -- 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/1349128 Title: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators) Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Confirmed Bug description: After upgrading to Unity version 7.2.2+14.04.20140714-0ubuntu1 on Trusty, the lockscreen sometimes fails to take the keyboard focus away from Chrome. This might happen if there's a text selection in Chrome, and also when resuming after suspend. It doesn't always happen, as this is a race condition, but it's easy to reproduce by selecting the location bar in Chrome and then locking the screen. Workaround: click on any indicator in the upper right corner, and close the menu. After that, keyboard input is sent to the lockscreen again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+subscriptions -- Mailing list: https://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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
Make sure you all have installed the unity package version 7.2.2+14.04.20140714-0ubuntu1.1 (use "apt-cache policy unity" to check), and you've restarted your session. -- 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059872] Re: Error formatting disk using disk utility
** Changed in: util-linux (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1059872 Title: Error formatting disk using disk utility Status in “udisks2” package in Ubuntu: Triaged Status in “util-linux” package in Ubuntu: Triaged Status in “util-linux” package in Debian: Fix Released Bug description: Formatting a SD card using the disk utility fails with an error message "Error formatting disk - Error synchronizing after initial wipe: Timed out waiting for object (udisks-error-quark, 0)" Steps to repro: Launch the disk utility Plug a SD card into the computer Select the SD card and click on the gears icon at the top right of the application From the drop down menu, select "Format Disk" maintain the default setting and select Format Acknowledge warnings After format process has been going for a while, the error message shown above pops up ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: udisks 1.0.4-6 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CustomUdevRuleFiles: 51-android.rules 51-android.rules~ Date: Mon Oct 1 15:07:46 2012 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120720.1) MachineType: FOXCONN NT-A2400&NT-A3500 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=fcc445e4-9662-47cc-855d-ca17ad1c2a87 ro quiet splash vt.handoff=7 SourcePackage: udisks UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: NT-A2400&NT-A3500 dmi.board.vendor: FOXCONN dmi.board.version: FAB 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 4 dmi.chassis.vendor: FOXCONN dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd03/29/2011:svnFOXCONN:pnNT-A2400&NT-A3500:pvrFAB1.0:rvnFOXCONN:rnNT-A2400&NT-A3500:rvrFAB1.0:cvnFOXCONN:ct4:cvrToBeFilledByO.E.M.: dmi.product.name: NT-A2400&NT-A3500 dmi.product.version: FAB 1.0 dmi.sys.vendor: FOXCONN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1059872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 939863] Re: Warning message from ffmpeg program needs update
Please restore ffmpeg. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/939863 Title: Warning message from ffmpeg program needs update Status in the libav multimedia framework: Fix Released Status in “libav” package in Ubuntu: Fix Released Status in “libav” source package in Precise: Fix Released Bug description: The warning message from the ffmpeg program needs to be updated. It should instead say "*** THIS PROGRAM IS DEPRECATED ***\n" "This program is only provided for compatibility " "and will be removed in a future release. Please " "use avconv instead.\n" This is patched in Debian. See [1]. [Impact] - Users are seeing a different message everytime they run the ffmpeg program. The original message is causing confusion amongst general users of the ffmpeg who are not aware that the ffmpeg program provided in Ubuntu is the ffmpeg program originally made available from the Libav project. [Development Fix] - Message just needs to be updated. See [1]. Note that the ffmpeg binary has been dropped completely in the development tree in libav. [Stable Fix] - See [1]. [Test Case] - Just run the ffmpeg program. Running 'ffmpeg -L' is sufficient to see the warning. The original warning reads, "This program is not developed anymore and is only " "provided for compatibility. Use avconv instead " "(see Changelog for the list of incompatible changes).\n" The new warning should read, "*** THIS PROGRAM IS DEPRECATED ***\n" "This program is only provided for compatibility " "and will be removed in a future release. Please " "use avconv instead.\n" [Regression Potential] - There's no potential regression. 1. http://anonscm.debian.org/gitweb/?p=pkg- multimedia/libav.git;a=blob;f=debian/patches/04-ffmpeg-warning- change.patch;h=0472d450a743ff0b3918c80e91da16d4c4b35d2b;hb=HEAD To manage notifications about this bug go to: https://bugs.launchpad.net/libav/+bug/939863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1208019] Re: Eclipse menus don't show up in Trusty
** Bug watch removed: Eclipse bugs #425614 https://bugs.eclipse.org/bugs/show_bug.cgi?id=425614 -- 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/1208019 Title: Eclipse menus don't show up in Trusty Status in Eclipse: Unknown Status in GTK+ GUI Toolkit: Fix Released Status in Unity GTK+ module: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “unity-gtk-module” package in Ubuntu: Fix Released Status in “gtk+3.0” source package in Trusty: Fix Committed Status in “unity-gtk-module” source package in Trusty: In Progress Bug description: [Impact] Switching tabs between open source files with different file types in Eclipse causes the Source and Refactor menus to be empty in the global menu bar under Unity. This is a severe usability problem for many Eclipse users. The fix proposed has been available in a PPA and is well-tested. [Test Case] 1. Open a new project in Eclipse. 2. Open two files: one with a .java extension, another with a .txt extension. 3. Switch between the .java file and the .txt file and back again. 4. Open the Source or Refactor menu in the Unity global menu bar. Expected result: menus with menu items Actual result: empty menus for both [Regression Potential] The fix involves changes to both gtk and unity-gtk-module. The changes to gtk are minimal and only involve the reversal of a pair of signal emissions, in a part of the code (GtkMenuTracker) which is normally used by desktop environments, not typical user applications. Therefore regression potential for the gtk update is unlikely. The changes to unity-gtk-module involve emitting show and hide signals where they were none before has some regression potential for applications that are explicitly watching for when their menus are opening and closing. But this is rare for applications to do, and we likely would have already received bug reports for those that do. Being completely sure would require extensive testing across all gtk apps though. Both changes together have been available as a PPA, thoroughly tested for quite some time now. [Other Info] The changes to unity-gtk-module depend on the changes to gtk, so both must be tested in simultaneity. Suggested to upload both to trusty- proposed at the same time. Original bug report follows: === %< === HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify "/usr/share/applications/eclipse.desktop" to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1208019] Re: Eclipse menus don't show up in Trusty
** Bug watch removed: Eclipse bugs #330563 https://bugs.eclipse.org/bugs/show_bug.cgi?id=330563 -- 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/1208019 Title: Eclipse menus don't show up in Trusty Status in Eclipse: Unknown Status in GTK+ GUI Toolkit: Fix Released Status in Unity GTK+ module: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “unity-gtk-module” package in Ubuntu: Fix Released Status in “gtk+3.0” source package in Trusty: Fix Committed Status in “unity-gtk-module” source package in Trusty: In Progress Bug description: [Impact] Switching tabs between open source files with different file types in Eclipse causes the Source and Refactor menus to be empty in the global menu bar under Unity. This is a severe usability problem for many Eclipse users. The fix proposed has been available in a PPA and is well-tested. [Test Case] 1. Open a new project in Eclipse. 2. Open two files: one with a .java extension, another with a .txt extension. 3. Switch between the .java file and the .txt file and back again. 4. Open the Source or Refactor menu in the Unity global menu bar. Expected result: menus with menu items Actual result: empty menus for both [Regression Potential] The fix involves changes to both gtk and unity-gtk-module. The changes to gtk are minimal and only involve the reversal of a pair of signal emissions, in a part of the code (GtkMenuTracker) which is normally used by desktop environments, not typical user applications. Therefore regression potential for the gtk update is unlikely. The changes to unity-gtk-module involve emitting show and hide signals where they were none before has some regression potential for applications that are explicitly watching for when their menus are opening and closing. But this is rare for applications to do, and we likely would have already received bug reports for those that do. Being completely sure would require extensive testing across all gtk apps though. Both changes together have been available as a PPA, thoroughly tested for quite some time now. [Other Info] The changes to unity-gtk-module depend on the changes to gtk, so both must be tested in simultaneity. Suggested to upload both to trusty- proposed at the same time. Original bug report follows: === %< === HOW TO REPRODUCE 1. Run Eclipse, Gimp or Inkscape. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) ** EXPECTED BEHAVIOUR ** - The content of the submenus show up. ** REAL BEHAVIOUR ** - Only the top-level headers are available. - Nothing happens when clicking on them - They don't show up in the HUD either. *** WORK-AROUND *** To modify "/usr/share/applications/eclipse.desktop" to look like this: [Desktop Entry] Type=Application Name=Eclipse Comment=Eclipse Integrated Development Environment Icon=eclipse Exec=env UBUNTU_MENUPROXY= eclipse Terminal=false Categories=Development;IDE;Java; RELEVANT DETAILS - Doesn't affect Ubuntu releases prior to 13.10. ** TECHNICAL INFO ** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1208019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 618587] Re: eclipse does not work with appmenu
** Bug watch removed: Eclipse bugs #419830 https://bugs.eclipse.org/bugs/show_bug.cgi?id=419830 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdbusmenu in Ubuntu. https://bugs.launchpad.net/bugs/618587 Title: eclipse does not work with appmenu Status in Application menu module for GTK+: Invalid Status in Audacity: Invalid Status in Eclipse: Unknown Status in The Application Menu: Invalid Status in DBus Menu: Fix Released Status in Unity Foundations: Fix Released Status in “libdbusmenu” package in Ubuntu: Fix Released Status in “libdbusmenu” source package in Natty: Won't Fix Bug description: Binary package hint: indicator-appmenu eclipse do not work ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: indicator-appmenu 0.0.9-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1 Uname: Linux 2.6.35-15-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Aug 16 13:06:20 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1) ProcEnviron: PATH=(custom, user) LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-appmenu To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-gtk/+bug/618587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 734908] Re: Unity is visible on top of fullscreen apps
I still have this bug in Ubuntu 14.04 (up to date) with Trine 2. When I accidentally press ALT, the unity launcher is always visible. -- 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/734908 Title: Unity is visible on top of fullscreen apps Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity Distro Priority: Confirmed Status in “compiz” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Confirmed Status in “unity” source package in Precise: Fix Released Bug description: [Test Case] 1. Start a fullscreen application (e.g. Firefox in Fullscreen mode) -> Verify that the panel is not visible [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: NOTE: This bug is only about the single monitor case. If you still have problems with multiple monitors, see bug 748539 instead. ORIGINAL DESCRIPTION: In natty alpha 3 up to date, I cannot get fullscreen in any application. Panels are still visible. Tested with: - totem - vlc - firefox - chrome - geany Unity panel and top bar are always on top. - Desired Solution: - When a window is fullscreen (note: this should not be confused with the *maximised* state) the menu bar should not be displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/734908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1088146] Re: Asus n56vz battery state is wrong or battery not charging at all.
Just happened on my ASUS N550J notebook, running 14.04. I ran `sudo apt-get update && sudo apt-get dist-upgrade` and waited to finish updating. Then I rebooted the machine, and everything seems to work fine now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1088146 Title: Asus n56vz battery state is wrong or battery not charging at all. Status in “upower” package in Ubuntu: Confirmed Bug description: I have an ASUS N56VZ notebook. There are some bugs I have mentioned and they are known on ubuntu forums. Sometimes I am getting strange results in battery power state, that are not even close to be accurate. So bugs are: 1) Then I am turning on the notebok with not enough power (3% for example) the fan is going to it`s full speed (no CPU loading at all) and the power indicator shows that power is insufficient. Plugging the power adapter didn`t solved the problem - it was not charging and notebook soon turns off. 2) As I described above, I can`t feed the notebook sometimes (especially on low battery level). 3) I am getting the strange battery state result: sometimes it looks, that it`s charging very slow. Am am working about a hour and my power level just rised from 30 minutes to 40 minutes. 4) I am not sure about this bug, may be it`s a hardware one, but then I turned notebook off with plugged in power adapter, it was not charged at all for the whole night! http://ubuntuforums.org/showthread.php?t=2084696 - here is a proof, that I am not alone ))) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: upower 0.9.17-1build1 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Dec 9 13:18:17 2012 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2012-11-30 (8 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1088146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351656] [NEW] no sound
Public bug reported: no sound + driver for video card appears to be missing ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-lowlatency 3.13.11.4 Uname: Linux 3.13.0-32-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin Date: Sat Aug 2 20:13:31 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-32-lowlatency, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450 AGP] [1002:95c6] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:0028] LightdmGreeterLog: ** (lightdm-gtk-greeter:1734): WARNING **: Failed to load user image: Openen van bestand ‘/home/pee/.face’ mislukt: Bestand of map bestaat niet init: indicator-power main process (1779) killed by TERM signal init: indicator-application main process (1788) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1733): WARNING **: Failed to load user image: Openen van bestand ‘/home/pee/.face’ mislukt: Bestand of map bestaat niet init: indicator-power main process (1778) killed by TERM signal init: indicator-application main process (1788) killed by TERM signal MachineType: MEDIONPC MS-7012 ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-lowlatency root=UUID=3d701baa-322f-4f29-ba7a-6b7714ecb09a ro splash quiet vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2003 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7012 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd09/29/2003:svnMEDIONPC:pnMS-7012:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7012:rvr:cvn:ct3:cvr: dmi.product.name: MS-7012 dmi.sys.vendor: MEDIONPC version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 2 20:01:01 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImPS/2 Generic Wheel Mouse MOUSE, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1351656 Title: no sound Status in “xorg” package in Ubuntu: New Bug description: no sound + driver for video card appears to be missing ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-lowlatency 3.13.11.4 Uname: Linux 3.13.0-32-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin Date: Sat Aug 2 20:13:31 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-32-lowlatency, i686: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450 AGP] [1002:95c6] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:0028] LightdmGreeterLog: ** (lightdm-gtk-greeter:1734): WARNING **: Failed to load user image: Openen van bestand ‘/home/pee/.face’ mislukt: Bestand of map bestaat niet init: indicator-power main process (1779) killed by TERM signal init: indicator-application main process (1788) killed by TERM signal LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1733): WARNING **: Failed to load user image: Openen van bestand ‘/home/pee/.face’ mislukt: Bestand of map bestaat niet init: indicator-p
[Touch-packages] [Bug 1351464] Re: Ubuntu 14.10 pulse audio broken
Try to reset the user config with the following command and then log out and back in:: rm -r ~/.config/pulse If it's still not working, please get a pulseaudio log: https://wiki.ubuntu.com/PulseAudio/Log ** Package changed: linux (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1351464 Title: Ubuntu 14.10 pulse audio broken Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: In Ubuntu 14.10 Pulse audio options dont work at all and there's no Audio option in the top right of the screen any more. Not sure if that is already getting worked on and changed to something else but likely to happen to alpha versions of Ubuntu ^_^ but thought it was something that ya peeps would like to know just in case. the audio works but the options are not able to work in system settings plus if 1 was to search for pulse audio through the browser of programs it cant find it --- ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: darkangel 14561 F...m java /dev/snd/controlC0: darkangel 14561 F java /dev/snd/timer: darkangel 14561 f java CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=569c56dd-f25c-4a2d-bd00-ca52486d4cea InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140731) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: eMachines EL1360G NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=db39e416-41db-4526-8c10-85c1fcfc8fe2 ro quiet splash ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1351464/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281019] Re: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331
Ingo Gerth, please stop toggling this report, as it's not scoped to you, your hardware, or your problem. If you have comments, please post them in the bug report you made. Thank you for your understanding. ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- 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/1281019 Title: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331 Status in “xorg” package in Ubuntu: Incomplete Bug description: The Brightness keys (FN+F9 and FN+FN10) are doing 'something' in the right corner of the screen the brightness control window does show-up and changes, but the brightness of the screen itself does not via Nvidia drivers version 319 or 331. There is the bugreport at the official Nvidia forums: https://devtalk.nvidia.com/default/topic/539462/linux/-nvidia-319-12-brightness-controls-not-working-on-laptop-ubuntu-13-03-/2/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia appassure_vss .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/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.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Mon Feb 17 10:05:44 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: appassure-vss, 5.3.6, 3.11.0-15-generic, x86_64: installed nvidia-331, 331.38, 3.11.0-15-generic, x86_64: installed nvidia-331-uvm, 331.38, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1631] MachineType: Hewlett-Packard HP EliteBook 8560w MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=caf0bb2d-fbef-46ff-be64-0ec601243262 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.99+git20140206.8de6f7b2-0ubuntu0sarvatt~saucy version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910+git20140210.5142d1ca-0ubuntu0sarvatt~saucy version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9+git20130730.300c5a32-0ubuntu0sarvatt xserver.bootTime: Mon Feb 17 10:03:57 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1281019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
Seems like it is fixed now, in the unity package: $ sudo apt-cache policy unity unity: Installert: 7.2.2+14.04.20140714-0ubuntu1.1 See changelog: https://launchpad.net/ubuntu/+source/unity/7.2.2+14.04.20140714-0ubuntu1.1 And the associated bug: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349128 -- 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, you can't enter your password in the lockscreen. [Test case] This will work only in the case that your lockscreen is set (from unity control center, lock pane) to lock immediately (when screen turns off). 1. Open a window that will hold the grab, such as the ssh password dialog or a virtual machine (such as virtualbox in fullscreen). 2. Wait for the lock screen to activate [1]. 3. The screen won't be locked, since it's not possible to steal drag to another window. [Regression potential] For the same reason of lp:49579, we can't lock the screen (yet) if something takes the grab in X, or we won't able to get input back. This is not a regression because it has never been possible in Ubuntu before, while when we tried that, it caused this bug. A possible source of regression might be that we now try to grab/ungrab the screen (the only X reliable way for grab checking), when showing the dash/hud or the lockscreen itself, and this might slow things down a little, but from measurements done this slow down is generally about 2ms, so nothing to worry about. * Compiz Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-trusty-sru-2.debdiff * [1] You can use this to reduce the locking delay: gsettings set org.gnome.desktop.session idle-delay 5 and resetting it with: gsettings reset org.gnome.desktop.session idle-delay --- Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351464] [NEW] Ubuntu 14.10 pulse audio broken
You have been subscribed to a public bug: In Ubuntu 14.10 Pulse audio options dont work at all and there's no Audio option in the top right of the screen any more. Not sure if that is already getting worked on and changed to something else but likely to happen to alpha versions of Ubuntu ^_^ but thought it was something that ya peeps would like to know just in case. the audio works but the options are not able to work in system settings plus if 1 was to search for pulse audio through the browser of programs it cant find it --- ApportVersion: 2.14.5-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: darkangel 14561 F...m java /dev/snd/controlC0: darkangel 14561 F java /dev/snd/timer: darkangel 14561 f java CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=569c56dd-f25c-4a2d-bd00-ca52486d4cea InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140731) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: eMachines EL1360G NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=db39e416-41db-4526-8c10-85c1fcfc8fe2 ro quiet splash ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-6-generic N/A linux-backports-modules-3.16.0-6-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected utopic -- Ubuntu 14.10 pulse audio broken https://bugs.launchpad.net/bugs/1351464 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351641] Re: Launcher icon title does not disappear automatically
I can confirm this happens to me as well, on every Ubuntu 14.04 machine I've encountered so far actually. -- 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/1351641 Title: Launcher icon title does not disappear automatically Status in “unity” package in Ubuntu: Confirmed Bug description: When you hover over an icon in the launcher bar with the cursor, a text field with the title of the application pops up. Usually this disappears as soon as you move the cursor away from the icon. However, it occasionally happens that the title does not disappear, and stays on screen even though the launcher bar is hidden again (I have auto- hide turned on). If that happens, you can get the title to disappear as it should by hovering the mouse over the same icon again and then moving it away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Sat Aug 2 18:33:50 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-27-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-29-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-30-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2014-04-23 (101 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20245 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e9acf7a8-4d74-4222-9079-5ec04553488a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7BCN36WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G500s dmi.modalias: dmi:bvnLENOVO:bvr7BCN36WW(V2.02):bd08/28/2013:svnLENOVO:pn20245:pvrLenovoG500s:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500s: dmi.product.name: 20245 dmi.product.version: Lenovo G500s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 2 17:53:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18002 vendor SDC xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351641] Re: Launcher icon title does not disappear automatically
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1351641 Title: Launcher icon title does not disappear automatically Status in “unity” package in Ubuntu: Confirmed Bug description: When you hover over an icon in the launcher bar with the cursor, a text field with the title of the application pops up. Usually this disappears as soon as you move the cursor away from the icon. However, it occasionally happens that the title does not disappear, and stays on screen even though the launcher bar is hidden again (I have auto- hide turned on). If that happens, you can get the title to disappear as it should by hovering the mouse over the same icon again and then moving it away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Sat Aug 2 18:33:50 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-27-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-29-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-30-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2014-04-23 (101 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20245 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e9acf7a8-4d74-4222-9079-5ec04553488a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7BCN36WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G500s dmi.modalias: dmi:bvnLENOVO:bvr7BCN36WW(V2.02):bd08/28/2013:svnLENOVO:pn20245:pvrLenovoG500s:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500s: dmi.product.name: 20245 dmi.product.version: Lenovo G500s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 2 17:53:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18002 vendor SDC xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351646] [NEW] SRU: gdb 7.7.1 for trusty
Public bug reported: SRU: gdb 7.7.1 for trusty ** Affects: gdb (Ubuntu) Importance: Undecided Status: New -- 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/1351646 Title: SRU: gdb 7.7.1 for trusty Status in “gdb” package in Ubuntu: New Bug description: SRU: gdb 7.7.1 for trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1351646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351641] [NEW] Launcher icon title does not disappear automatically
Public bug reported: When you hover over an icon in the launcher bar with the cursor, a text field with the title of the application pops up. Usually this disappears as soon as you move the cursor away from the icon. However, it occasionally happens that the title does not disappear, and stays on screen even though the launcher bar is hidden again (I have auto-hide turned on). If that happens, you can get the title to disappear as it should by hovering the mouse over the same icon again and then moving it away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 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: Sat Aug 2 18:33:50 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-27-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-29-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-30-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2014-04-23 (101 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20245 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=e9acf7a8-4d74-4222-9079-5ec04553488a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7BCN36WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G500s dmi.modalias: dmi:bvnLENOVO:bvr7BCN36WW(V2.02):bd08/28/2013:svnLENOVO:pn20245:pvrLenovoG500s:rvnLENOVO:rnINVALID:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG500s: dmi.product.name: 20245 dmi.product.version: Lenovo G500s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 2 17:53:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18002 vendor SDC xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1351641 Title: Launcher icon title does not disappear automatically Status in “unity” package in Ubuntu: New Bug description: When you hover over an icon in the launcher bar with the cursor, a text field with the title of the application pops up. Usually this disappears as soon as you move the cursor away from the icon. However, it occasionally happens that the title does not disappear, and stays on screen even though the launcher bar is hidden again (I have auto- hide turned on). If that happens, you can get the title to disappear as it should by hovering the mouse over the same icon again and then moving it away. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composit
[Touch-packages] [Bug 1343970] Re: gst-plugins-good pkg-config file issues
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gst-plugins-good1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1343970 Title: gst-plugins-good pkg-config file issues Status in “gst-plugins-good1.0” package in Ubuntu: Confirmed Bug description: Came across a small bug while trying to build the gst-rtsp-server-1.2.3. Using Ubuntu 14.04, and gst-plugins installed from the official ubuntu repositories. While building, it tries to use the gstreamer-plugins-good-1.0.pc pkg-config file (which has pluginsdir missing). 1. If libgstreamer-plugins-good1.0-dev_1.2.4-1~ubuntu1_i386.deb is removed (which removes the .pc file too), the rtsp-server builds fine. 2. Another fix will be to add the pluginsdir in the .pc file (The debian package should be modified ). After reading up a bit more, I came across this in gst-check.m4 "dnl Will set GST_PLUGINS_GOOD_DIR for use in Makefile.am. Note that this will dnl only be set in an uninstalled setup, since -good ships no .pc file and in dnl an installed setup all plugins will be found in GST_PLUGINS_DIR anyway." Hence there shouldn't be a .pc file for gst-plugins-good anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1343970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343970] Re: gst-plugins-good pkg-config file issues
Hello, GStreamer developer here. Could someone please bump up the severity of this ticket ? What ubuntu is doing here is really broken and simply not okay. It would be great if it could be sorted out quickly. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1343970 Title: gst-plugins-good pkg-config file issues Status in “gst-plugins-good1.0” package in Ubuntu: Confirmed Bug description: Came across a small bug while trying to build the gst-rtsp-server-1.2.3. Using Ubuntu 14.04, and gst-plugins installed from the official ubuntu repositories. While building, it tries to use the gstreamer-plugins-good-1.0.pc pkg-config file (which has pluginsdir missing). 1. If libgstreamer-plugins-good1.0-dev_1.2.4-1~ubuntu1_i386.deb is removed (which removes the .pc file too), the rtsp-server builds fine. 2. Another fix will be to add the pluginsdir in the .pc file (The debian package should be modified ). After reading up a bit more, I came across this in gst-check.m4 "dnl Will set GST_PLUGINS_GOOD_DIR for use in Makefile.am. Note that this will dnl only be set in an uninstalled setup, since -good ships no .pc file and in dnl an installed setup all plugins will be found in GST_PLUGINS_DIR anyway." Hence there shouldn't be a .pc file for gst-plugins-good anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1343970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351308] Re: Changing language has no effect
Changing language works on an updated utopic desktop with accountsservice 0.6.37-1ubuntu7. Can it be that some library needs to be added to the touch image rather than changing accountsservice? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1351308 Title: Changing language has no effect Status in “accountsservice” package in Ubuntu: Confirmed Bug description: broken on mako #164 Last known good image: #163 TEST CASE: 1. On a device in English, go to "System Settings/Language & Text/Display Language" 2. Scroll down the list and select another language i.e "Français (France)" 3. Tap "Confirm" ACTUAL RESULT Language did not change (the label in front of "Display language" is still English) and is still English (even after a reboot) EXPECTED LANGUAGE Setting is set to French and UI is localized after a reboot. Same problem with the wizard. The language changes *inside* the wizard but changes are not written to ~/.pam_environment Downgrading accountsservice to 0.6.37-1ubuntu6 on #167 fixes the issue Upgrading accountsservice to 0.6.37-1ubuntu7 on #164 reproduces the issue ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140730-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu2 Architecture: armhf Date: Fri Aug 1 15:05:35 2014 InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140801-020205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1351308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281019] Re: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331
** Changed in: xorg (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1281019 Title: 10de:0dda [HP EliteBook 8560w] Brightness controls are not working nvidia-319 and nvidia-331 Status in “xorg” package in Ubuntu: Confirmed Bug description: The Brightness keys (FN+F9 and FN+FN10) are doing 'something' in the right corner of the screen the brightness control window does show-up and changes, but the brightness of the screen itself does not via Nvidia drivers version 319 or 331. There is the bugreport at the official Nvidia forums: https://devtalk.nvidia.com/default/topic/539462/linux/-nvidia-319-12-brightness-controls-not-working-on-laptop-ubuntu-13-03-/2/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia appassure_vss .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/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.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Mon Feb 17 10:05:44 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: appassure-vss, 5.3.6, 3.11.0-15-generic, x86_64: installed nvidia-331, 331.38, 3.11.0-15-generic, x86_64: installed nvidia-331-uvm, 331.38, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1631] MachineType: Hewlett-Packard HP EliteBook 8560w MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=caf0bb2d-fbef-46ff-be64-0ec601243262 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.99+git20140206.8de6f7b2-0ubuntu0sarvatt~saucy version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910+git20140210.5142d1ca-0ubuntu0sarvatt~saucy version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9+git20130730.300c5a32-0ubuntu0sarvatt xserver.bootTime: Mon Feb 17 10:03:57 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1281019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350017] Re: [clock-app] There is no vibration when an alarm goes off
** Branch linked: lp:~nik90/ubuntu-clock-app/add-vibration-support ** Changed in: ubuntu-clock-app Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1350017 Title: [clock-app] There is no vibration when an alarm goes off Status in Clock application for Ubuntu devices: In Progress Status in Ubuntu UX bugs: New Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: It'd be probably nice to also have vibration beside the sound alert when an alarm triggers. - Design Solution -- Giorgio Venturi updated the design spec for the clock app at [1]. The vibration will be enabled by default for all alarms. The user however will be provided a global setting to disable that if required. [1] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351528] Re: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time
adding kernel parameter lvmwait=2 also works around this issue (source of idea http://serverfault.com/questions/567579/boot-failure-with-root-on-md-raid1-lvm-udev-event-timing) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1351528 Title: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time Status in “lvm2” package in Ubuntu: New Bug description: Trusty installation is combined root + /boot within LVM on top of mdraid (type 1.x) RAID1 with one missing disk (degraded). [method: basically create the setup in shell first then point install at the lvm. at end of install create a chroot and add mdadm pkg] boot fails with the following messages: Incrementally starting RAID arrays... mdadm: CREATE user root not found mdadm: CREATE group disk not found Incrementally starting RAID arrays... and slowly repeats the above at this point. workaround: - add break=premount to grub kernel line entry - for continue visibility of boot output also remove quiet, splash and possibly set gxmode 640x480 now @ initramfs prompt: mdadm --detail /dev/md0 should indicate a state of clean, degraded, array is started so this part is ok lvm lvs output attributes are as follows: -wi-d (instead of the expected -wi-a) lvs manpage this means device tables are missing (device mapper?) FIX: simply run lvm vgchange -ay and exit initramsfs. This will lead to a booting system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349128] Re: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators) Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Confirmed Bug description: After upgrading to Unity version 7.2.2+14.04.20140714-0ubuntu1 on Trusty, the lockscreen sometimes fails to take the keyboard focus away from Chrome. This might happen if there's a text selection in Chrome, and also when resuming after suspend. It doesn't always happen, as this is a race condition, but it's easy to reproduce by selecting the location bar in Chrome and then locking the screen. Workaround: click on any indicator in the upper right corner, and close the menu. After that, keyboard input is sent to the lockscreen again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
I don't know why the configuration provided by fonts-droid package makes fontconfig match UMing first as "Droid Sans Fallback". That is so weird. Howver, removing fonts-droid eliminates the problem succesefully. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: New Status in “language-selector” package in Ubuntu: New Bug description: There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing CN" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai CN" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351528] Re: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time
** Summary changed: - boot fails on raid (md raid1) + LVM (combined / + /boot) + degraded + boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1351528 Title: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time Status in “lvm2” package in Ubuntu: New Bug description: Trusty installation is combined root + /boot within LVM on top of mdraid (type 1.x) RAID1 with one missing disk (degraded). [method: basically create the setup in shell first then point install at the lvm. at end of install create a chroot and add mdadm pkg] boot fails with the following messages: Incrementally starting RAID arrays... mdadm: CREATE user root not found mdadm: CREATE group disk not found Incrementally starting RAID arrays... and slowly repeats the above at this point. workaround: - add break=premount to grub kernel line entry - for continue visibility of boot output also remove quiet, splash and possibly set gxmode 640x480 now @ initramfs prompt: mdadm --detail /dev/md0 should indicate a state of clean, degraded, array is started so this part is ok lvm lvs output attributes are as follows: -wi-d (instead of the expected -wi-a) lvs manpage this means device tables are missing (device mapper?) FIX: simply run lvm vgchange -ay and exit initramsfs. This will lead to a booting system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
OK, after I removed fonts-droid package and installed those testing packages and configurations which using "Droid Sans Fallback" instead of "Droid Sans" today, everything seems to be good. Below are my testing results, LANG=zh_TW.UTF-8 fc-match -s "Droid Sans" | head -n 10 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing TW" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai TW" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold" Waree.ttf: "Waree" "Book" ukai.ttc: "AR PL UKai CN" "Book" uming.ttc: "AR PL UMing CN" "Light" KhmerOS.ttf: "Khmer OS" "Regular" LANG=zh_TW.UTF-8 fc-match -s "sans-serif" | head -n 10 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing TW" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai TW" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold" Waree.ttf: "Waree" "Book" ukai.ttc: "AR PL UKai CN" "Book" uming.ttc: "AR PL UMing CN" "Light" KhmerOS.ttf: "Khmer OS" "Regular" LANG=zh_TW.UTF-8 fc-match -s "Droid Sans Fallback" | head -n 10 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing TW" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai TW" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold" Waree.ttf: "Waree" "Book" ukai.ttc: "AR PL UKai CN" "Book" uming.ttc: "AR PL UMing CN" "Light" KhmerOS.ttf: "Khmer OS" "Regular" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: New Status in “language-selector” package in Ubuntu: New Bug description: There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing CN" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai CN" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351610] [NEW] LightDM looses focus
Public bug reported: Sometimes after I wake up from suspend, LightDM seems to lost focus to a window in the desktop. I have a blinking cursor in the LightDM screen, and if I start typing anything the cursor doesn't move, and the only way to bypass this is wait the screen to turn off and on again (here I can type the password). This also happens when locking the screen. Description:Ubuntu 14.04.1 LTS Release:14.04 Lightdm version: 1.10.1-0ubuntu1 How to reproduce: * Open a window and click on a text box (ex: login form in some web page in a browser). * Lock the screen * Try to type your password to unlock it: the cursor blinks but doesn't move at all; * Wait for the screen to turn off, do something to wake up the screen and login; * Whatever you typed will be on the text input of the window you had focus (in this example: the login form of the web page) What was supposed to happen: * After locking the screen or waking from suspend, I expected that typing my password would unlock the screen. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Description changed: Sometimes after I wake up from suspend, LightDM seems to lost focus to a window in the desktop. - I have a blinking cursor and if I start typing anything the cursor doesn't move, and the only way to bypass this is wait the screen to turn off and on again (here I can type the password). + I have a blinking cursor in the LightDM screen, and if I start typing anything the cursor doesn't move, and the only way to bypass this is wait the screen to turn off and on again (here I can type the password). This also happens when locking the screen. Description: Ubuntu 14.04.1 LTS Release: 14.04 Lightdm version: 1.10.1-0ubuntu1 How to reproduce: - * Open a window and get click on a text box (ex: login form in some web page in a browser). + * Open a window and click on a text box (ex: login form in some web page in a browser). * Lock the screen * Try to type your password to unlock it: the cursor blinks but doesn't move at all; * Wait for the screen to turn off, do something to wake up the screen and login; * Whatever you typed will be on the text input of the window you had focus (in this example: the login form of the web page) What was supposed to happen: * After locking the screen or waking from suspend, I expected that typing my password would unlock the screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1351610 Title: LightDM looses focus Status in “lightdm” package in Ubuntu: New Bug description: Sometimes after I wake up from suspend, LightDM seems to lost focus to a window in the desktop. I have a blinking cursor in the LightDM screen, and if I start typing anything the cursor doesn't move, and the only way to bypass this is wait the screen to turn off and on again (here I can type the password). This also happens when locking the screen. Description: Ubuntu 14.04.1 LTS Release: 14.04 Lightdm version: 1.10.1-0ubuntu1 How to reproduce: * Open a window and click on a text box (ex: login form in some web page in a browser). * Lock the screen * Try to type your password to unlock it: the cursor blinks but doesn't move at all; * Wait for the screen to turn off, do something to wake up the screen and login; * Whatever you typed will be on the text input of the window you had focus (in this example: the login form of the web page) What was supposed to happen: * After locking the screen or waking from suspend, I expected that typing my password would unlock the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1351610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351609] [NEW] cannot enter a long number with 22 digits
Public bug reported: It is not possible to enter long numbers into the dialog it seems to stop after 20 digits. Long numbers are necessary for charging prepaid sim cards. It worked for me by dialing the number using ofono scripts. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- 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/1351609 Title: cannot enter a long number with 22 digits Status in “dialer-app” package in Ubuntu: New Bug description: It is not possible to enter long numbers into the dialog it seems to stop after 20 digits. Long numbers are necessary for charging prepaid sim cards. It worked for me by dialing the number using ofono scripts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1351609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 736788] Re: 13d3:3304 IMC Networks bluetooth doesn't work
I wonder if there is a workaround to at least unload the module / re- load after resuming from suspend -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/736788 Title: 13d3:3304 IMC Networks bluetooth doesn't work Status in “bluez” package in Ubuntu: Confirmed Bug description: Binary package hint: bluez The "13d3:3304 IMC Networks" internal bluetooth module found in Asus U36JC notebook is not working in Ubuntu Maverick nor Natty. The systems certainly knows about presence of the bluetooth module - the icon in status bar is visible and allows to switch it on/off, but nothing else works. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7 Uname: Linux 2.6.38-6-generic x86_64 Architecture: amd64 CheckboxSubmission: 4c3a0145220348e366d02efaed27e66e CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 Date: Thu Mar 17 12:03:47 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302) InterestingModules: sco bnep l2cap btusb bluetooth MachineType: ASUSTeK Computer Inc. U36JC ProcEnviron: LANGUAGE=cs_CZ:en PATH=(custom, user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic root=UUID=2d566c56-67c7-4af1-a443-a8c80061120c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36JC.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36JC 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.:bvrU36JC.205:bd01/26/2011:svnASUSTeKComputerInc.:pnU36JC:pvr1.0:rvnASUSTeKComputerInc.:rnU36JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U36JC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/736788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 736788] Re: 13d3:3304 IMC Networks bluetooth doesn't work
I'm encountering this not working after a suspend / resume cycle. on a clean boot, it seems to work. this is on an Asus UX32LN -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/736788 Title: 13d3:3304 IMC Networks bluetooth doesn't work Status in “bluez” package in Ubuntu: Confirmed Bug description: Binary package hint: bluez The "13d3:3304 IMC Networks" internal bluetooth module found in Asus U36JC notebook is not working in Ubuntu Maverick nor Natty. The systems certainly knows about presence of the bluetooth module - the icon in status bar is visible and allows to switch it on/off, but nothing else works. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7 Uname: Linux 2.6.38-6-generic x86_64 Architecture: amd64 CheckboxSubmission: 4c3a0145220348e366d02efaed27e66e CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 Date: Thu Mar 17 12:03:47 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302) InterestingModules: sco bnep l2cap btusb bluetooth MachineType: ASUSTeK Computer Inc. U36JC ProcEnviron: LANGUAGE=cs_CZ:en PATH=(custom, user) LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic root=UUID=2d566c56-67c7-4af1-a443-a8c80061120c ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: U36JC.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: U36JC 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.:bvrU36JC.205:bd01/26/2011:svnASUSTeKComputerInc.:pnU36JC:pvr1.0:rvnASUSTeKComputerInc.:rnU36JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: U36JC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:3 acl:0 sco:0 commands:1 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/736788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1260884] Re: Please update glew to 1.10.0
Glew 1.10.0 has been in Ubuntu for quit some time, and it looks like the other packages added in comment #4 has been rebuilt since it landed, should these tasks be closed too? -- 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/1260884 Title: Please update glew to 1.10.0 Status in Unity: Confirmed Status in “glew” package in Ubuntu: Fix Released Status in “nux” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: The current version of glew in ubuntu is outdated and blocking other updates. Can someone please update to 1.10, which might break other packages. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1260884/+subscriptions -- Mailing list: https://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 1351424] Re: browser, settings and calculator icons too similar to another well known mobile O/S
Silo 3 with Q of On Sat, Aug 2, 2014 at 2:23 PM, Sam Bull wrote: > I'd also like to point out that some of these icons don't even make > sense. A quote taken from http://asktog.com/atc/principles-of- > interaction-design/ : > > "The inverse of skeuomorphism is abstraction, a prominent feature in so- > called flat design, a fashion that took hold in 2013, turning once well- > understood icons and other elements into meaningless abstractions and > even false symbols. (For example, the icon for the browser on the iPhone > became a compass, only connected to the concept of the web through the > vaguest of abstractions. The iPhone has an actual compass, so they > turned its icon into… another compass! Two compass icons: One tells you > which way is north and the other connects you to your bank account. The > Settings icon had originally looked like the inner workings of a clock, > clearly carrying the message that this is an app that will let you see > and affect the inside workings of the iPhone. That was abstracted to the > point that it looks exactly like a large industrial fan.)" > > -- > You received this bug notification because you are subscribed to Ubuntu > Touch Core Apps. > Matching subscriptions: Touch Core Apps Bugs, Unity 8 > https://bugs.launchpad.net/bugs/1351424 > > Title: > browser, settings and calculator icons too similar to another well > known mobile O/S > > Status in Camera App: > New > Status in Calculator application for Ubuntu devices: > New > Status in Ubuntu UX bugs: > New > Status in Web Browser App: > New > Status in “ubuntu-system-settings” package in Ubuntu: > New > Status in “unity8” package in Ubuntu: > Invalid > > Bug description: > The browser and system settings icons in image #165 looks extremely > similar in both content and colour to another well-known mobile > operating system. IMHO they are also too busy > > Please can we change these to make them simpler and more uniquely > Ubuntu. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/camera-app/+bug/1351424/+subscriptions > -- 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/1351424 Title: browser, settings and calculator icons too similar to another well known mobile O/S Status in Camera App: New Status in Calculator application for Ubuntu devices: New Status in Ubuntu UX bugs: New Status in Web Browser App: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: The browser and system settings icons in image #165 looks extremely similar in both content and colour to another well-known mobile operating system. IMHO they are also too busy Please can we change these to make them simpler and more uniquely Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1351424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351424] Re: browser, settings and calculator icons too similar to another well known mobile O/S
I'd also like to point out that some of these icons don't even make sense. A quote taken from http://asktog.com/atc/principles-of- interaction-design/ : "The inverse of skeuomorphism is abstraction, a prominent feature in so- called flat design, a fashion that took hold in 2013, turning once well- understood icons and other elements into meaningless abstractions and even false symbols. (For example, the icon for the browser on the iPhone became a compass, only connected to the concept of the web through the vaguest of abstractions. The iPhone has an actual compass, so they turned its icon into… another compass! Two compass icons: One tells you which way is north and the other connects you to your bank account. The Settings icon had originally looked like the inner workings of a clock, clearly carrying the message that this is an app that will let you see and affect the inside workings of the iPhone. That was abstracted to the point that it looks exactly like a large industrial fan.)" -- 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/1351424 Title: browser, settings and calculator icons too similar to another well known mobile O/S Status in Camera App: New Status in Calculator application for Ubuntu devices: New Status in Ubuntu UX bugs: New Status in Web Browser App: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: The browser and system settings icons in image #165 looks extremely similar in both content and colour to another well-known mobile operating system. IMHO they are also too busy Please can we change these to make them simpler and more uniquely Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1351424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351590] Re: Cannot configure wi-fi in a Xubuntu live-session without logging out and back in again
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1351590 ** Tags added: iso-testing -- 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/1351590 Title: Cannot configure wi-fi in a Xubuntu live-session without logging out and back in again Status in “network-manager” package in Ubuntu: New Bug description: I am using the daily build 20140802 of Xubuntu in a live session and cannot setup a wi-fi connection as I am told I do not have the authority. See attached screenshot of error. If I log out and then back in again I can setup wifi without a problem. I first saw this problem with 20140801 but did not report it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CasperVersion: 1.340build1 CurrentDesktop: XFCE Date: Sat Aug 2 10:41:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.10 metric 9 LiveMediaBuild: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140802) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: samsung-wlan: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH virginmedia817089421b2f951-16f3-4abf-b20c-90d33ad3caf0 802-11-wireless 1406976080 Sat 02 Aug 2014 10:41:20 AM UTCyes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 11bcd9f7f-a0b6-421e-aadb-7d200a9e52de 802-3-ethernet1406975781 Sat 02 Aug 2014 10:36:21 AM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351590] Re: Cannot configure wi-fi in a Xubuntu live-session without logging out and back in again
As an afterthought - I'm not seeing this problem with Kubuntu, Ubuntu, Lubuntu or Ubuntu GNOME, only Xubuntu. -- 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/1351590 Title: Cannot configure wi-fi in a Xubuntu live-session without logging out and back in again Status in “network-manager” package in Ubuntu: New Bug description: I am using the daily build 20140802 of Xubuntu in a live session and cannot setup a wi-fi connection as I am told I do not have the authority. See attached screenshot of error. If I log out and then back in again I can setup wifi without a problem. I first saw this problem with 20140801 but did not report it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CasperVersion: 1.340build1 CurrentDesktop: XFCE Date: Sat Aug 2 10:41:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.10 metric 9 LiveMediaBuild: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140802) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: samsung-wlan: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH virginmedia817089421b2f951-16f3-4abf-b20c-90d33ad3caf0 802-11-wireless 1406976080 Sat 02 Aug 2014 10:41:20 AM UTCyes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 11bcd9f7f-a0b6-421e-aadb-7d200a9e52de 802-3-ethernet1406975781 Sat 02 Aug 2014 10:36:21 AM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351590] [NEW] Cannot configure wi-fi in a Xubuntu live-session without logging out and back in again
Public bug reported: I am using the daily build 20140802 of Xubuntu in a live session and cannot setup a wi-fi connection as I am told I do not have the authority. See attached screenshot of error. If I log out and then back in again I can setup wifi without a problem. I first saw this problem with 20140801 but did not report it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CasperVersion: 1.340build1 CurrentDesktop: XFCE Date: Sat Aug 2 10:41:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.10 metric 9 LiveMediaBuild: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140802) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: samsung-wlan: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH virginmedia817089421b2f951-16f3-4abf-b20c-90d33ad3caf0 802-11-wireless 1406976080 Sat 02 Aug 2014 10:41:20 AM UTCyes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 11bcd9f7f-a0b6-421e-aadb-7d200a9e52de 802-3-ethernet1406975781 Sat 02 Aug 2014 10:36:21 AM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug iso-testing live-session utopic xubuntu ** Attachment added: "Screenshot - 08022014 - 10:38:02 AM.png" https://bugs.launchpad.net/bugs/1351590/+attachment/4167944/+files/Screenshot%20-%2008022014%20-%2010%3A38%3A02%20AM.png ** Tags added: live-session xubuntu -- 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/1351590 Title: Cannot configure wi-fi in a Xubuntu live-session without logging out and back in again Status in “network-manager” package in Ubuntu: New Bug description: I am using the daily build 20140802 of Xubuntu in a live session and cannot setup a wi-fi connection as I am told I do not have the authority. See attached screenshot of error. If I log out and then back in again I can setup wifi without a problem. I first saw this problem with 20140801 but did not report it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CasperVersion: 1.340build1 CurrentDesktop: XFCE Date: Sat Aug 2 10:41:23 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.10 metric 9 LiveMediaBuild: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140802) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: samsung-wlan: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH virginmedia817089421b2f951-16f3-4abf-b20c-90d33ad3caf0 802-11-wireless 1406976080 Sat 02 Aug 2014 10:41:20 AM UTCyes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 11bcd9f7f-a0b6-421e-aadb-7d200a9e52de 802-3-ethernet1406975781 Sat 02 Aug 2014 10:36:21 AM UTC
[Touch-packages] [Bug 1351591] [NEW] menus on wrong monitor in multi-monitor layout with scaling
Public bug reported: The panel menus (from network to system) open on the wrong display in a multi monitor setup under the following circumstances: * left display has UI scaling 2.0 * right display has UI scaling 1.0 * menu is clicked on the left display The menu flies out on the right display although it was clicked on the left one. This does not happen when the non-scaled display is on the left, or when the menu is clicked on the right display. ubuntu: utopic unicorn (daily from 28.7) unity: 7.3 tested in VirtualBox ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot of the situation" https://bugs.launchpad.net/bugs/1351591/+attachment/4167956/+files/menus-multi-monitor-with-scaling.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1351591 Title: menus on wrong monitor in multi-monitor layout with scaling Status in “unity” package in Ubuntu: New Bug description: The panel menus (from network to system) open on the wrong display in a multi monitor setup under the following circumstances: * left display has UI scaling 2.0 * right display has UI scaling 1.0 * menu is clicked on the left display The menu flies out on the right display although it was clicked on the left one. This does not happen when the non-scaled display is on the left, or when the menu is clicked on the right display. ubuntu: utopic unicorn (daily from 28.7) unity: 7.3 tested in VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295909] Re: Unity spread trigger ruins windows and freezes desktop
I don't know why it was broken on a fresh install but this fixed the problem for me: http://speculator.diandian.com/post/2014-07-01/40062129998 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1295909 Title: Unity spread trigger ruins windows and freezes desktop Status in Compiz: Triaged Status in Unity: Confirmed Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: The latest update disabled window spreading and when triggered crashes the desktop. Everything freezes and windows cannot be switched. The only way to close an application is to shut down. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 21 20:59:17 2014 DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (77 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: TOSHIBA Satellite C55-A ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-18-generic root=UUID=6b37c83b-b64c-42fc-89d3-3db46a397734 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-20 (1 days ago) dmi.bios.date: 04/12/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.10 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.10:bd04/12/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCF6U-01Y00C:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C55-A dmi.product.version: PSCF6U-01Y00C dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 10.0.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 21 18:56:33 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17223 vendor SDC xserver.version: 2:1.15.0-1ubuntu7 --- .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-19-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (83 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: TOSHIBA Satellite C55-A Package: unity PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.
[Touch-packages] [Bug 1347147] Re: krb5 database operations enter infinite loop
This bug was fixed in the package gcc-4.9 - 4.9.1-4ubuntu2 --- gcc-4.9 (4.9.1-4ubuntu2) utopic; urgency=medium * Update to SVN 20140802 (r213510) from the gcc-4_9-branch. - Fix PR tree-optimization/61964. LP: #1347147. * Fix libphobos cross build. -- Matthias KloseSat, 02 Aug 2014 02:44:59 +0200 ** Changed in: gcc-4.9 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1347147 Title: krb5 database operations enter infinite loop Status in The GNU Compiler Collection: Unknown Status in Network Authentication System: Unknown Status in “gcc-4.8” package in Ubuntu: Fix Released Status in “gcc-4.9” package in Ubuntu: Fix Released Status in “krb5” package in Ubuntu: Triaged Status in “gcc-4.8” source package in Trusty: New Status in “krb5” source package in Trusty: New Bug description: [Impact] On krb5 KDC databases with more than a few hundred principals, operations can enter an infinite loop in the database library. This affects both read and write operations. If operators are fortunate, they will encounter this bug while testing a migration. If they are not so fortunate, they will encounter this bug in a production KDC when the number of principals crosses the threshold where this bug manifests, resulting in a service outage and possible database corruption. Probably the only way to restore service in that situation is to install a patched KDC or to downgrade to an unaffected version. Both Trusty and Utopic amd64 have been verified to have this issue. One concrete reported example is an invocation of kdb5_util load (as part of a slave KDC propagation) spinning: http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html Additional failure modes are likely A branch is linked including the upstream work around for this bug, along with two other patches to bugs already nominated for trusty applied to the krb5 in trusty. For utopic, the simplest fix is to rebuild krb5 with the compiler currently in utopic. An alternative is to request that the Debian maintainers (both monitoring this bug for such a request) upload the upstream work around to Debian and sync that. You could do an ubuntu- specific upload but it seems undesirable to introduce a change between Ubuntu and Debian when all the right parties are happy to avoid it. The upstream patch works around a compiler optimizer bug in the gcc-4.8 series, which incorrectly deduces that a strict aliasing violation has occurred and miscompiles part of the bundled libdb2 library that the KDC database back end depends upon. The miscompilation causes a data structure to contain an inappropriate cycle, which leads to an infinite loop when the structure is traversed. [Test Case] apt-get install krb5-kdc krb5-admin-server kdb5_util -W -r T create -s awk 'BEGIN{ for (i = 0; i < 1024; i++) { printf("ank -randkey a%06d\n", i) } }' /dev/null | kadmin.local -r T (Enter any password for the master key when requested.) On platforms with this issue, kadmin.local spins consuming 100% CPU after a few hundred principals have been created. (This is "a000762" on two examples.) To clean up, rm /etc/krb5kdc/principal* or krb5kdc -r T destroy but the latter can possibly enter the same infinite loop. [Regression Potential] Negligible. It is theoretically possible that our upstream workaround, which involves using TAILQ macros instead of CIRCLEQ macros in the bundled libdb2 that backs the KDC database, will have some as-yet undiscovered bugs or compiler interactions with consequences worse than this current issue. I think this is rather unlikely. The patched libdb2 passes both the extensive libdb2 test suite and the rest of the krb5 test suite. Prior to patching, compiling krb5 with an affected gcc would cause the krb5 test suite to stall when it reached the libdb2 test suite. (The test suite stall is how we became aware of the gcc optimizer bug.) The BSD TAILQ macros are generally considered to be safer than the CIRCLEQ macros, and the various open-source BSD derivatives have made the corresponding change to their libdb sources years ago, with no reported ill effects that I can see. Original report from Ben Kaduk: == In some conditions, propagating a kerberos database to a slave KDC server can stall. This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros, apparently due to overzealous strict aliasing deductions. One case of this stall is reported at http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html (and the rest of the thread), and there is an entry in the upstream bugtracker at http://krbdev.mit.edu/rt/Ticket/Display.html?id=
[Touch-packages] [Bug 1351308] Re: Changing language has no effect
** Description changed: - broken on mako #165 + broken on mako #164 Last known good image: #163 TEST CASE: 1. On a device in English, go to "System Settings/Language & Text/Display Language" 2. Scroll down the list and select another language i.e "Français (France)" 3. Tap "Confirm" ACTUAL RESULT Language did not change (the label in front of "Display language" is still English) and is still English (even after a reboot) EXPECTED LANGUAGE Setting is set to French and UI is localized after a reboot. Same problem with the wizard. The language changes *inside* the wizard but changes are not written to ~/.pam_environment + + Downgrading accountsservice to 0.6.37-1ubuntu6 on #167 fixes the issue + Upgrading accountsservice to 0.6.37-1ubuntu7 on #164 reproduces the issue + + ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140730-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu2 Architecture: armhf Date: Fri Aug 1 15:05:35 2014 InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140801-020205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1351308 Title: Changing language has no effect Status in “accountsservice” package in Ubuntu: Confirmed Bug description: broken on mako #164 Last known good image: #163 TEST CASE: 1. On a device in English, go to "System Settings/Language & Text/Display Language" 2. Scroll down the list and select another language i.e "Français (France)" 3. Tap "Confirm" ACTUAL RESULT Language did not change (the label in front of "Display language" is still English) and is still English (even after a reboot) EXPECTED LANGUAGE Setting is set to French and UI is localized after a reboot. Same problem with the wizard. The language changes *inside* the wizard but changes are not written to ~/.pam_environment Downgrading accountsservice to 0.6.37-1ubuntu6 on #167 fixes the issue Upgrading accountsservice to 0.6.37-1ubuntu7 on #164 reproduces the issue ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140730-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu2 Architecture: armhf Date: Fri Aug 1 15:05:35 2014 InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140801-020205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1351308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295909] Re: Unity spread trigger ruins windows and freezes desktop
I just want to emphasize that this is a bug with Unity. I have not used Unity Tweak Tool before this bug appeared. It started right after a fresh install on my new desktop system. I do not see this bug on any of my laptops. I'd be happy to do anything necessary to solve this annoying bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1295909 Title: Unity spread trigger ruins windows and freezes desktop Status in Compiz: Triaged Status in Unity: Confirmed Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: The latest update disabled window spreading and when triggered crashes the desktop. Everything freezes and windows cannot be switched. The only way to close an application is to shut down. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 21 20:59:17 2014 DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (77 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: TOSHIBA Satellite C55-A ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-18-generic root=UUID=6b37c83b-b64c-42fc-89d3-3db46a397734 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-20 (1 days ago) dmi.bios.date: 04/12/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.10 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.10:bd04/12/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCF6U-01Y00C:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C55-A dmi.product.version: PSCF6U-01Y00C dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 10.0.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 21 18:56:33 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17223 vendor SDC xserver.version: 2:1.15.0-1ubuntu7 --- .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-19-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (83 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Relea
[Touch-packages] [Bug 1295909] Re: Unity spread trigger ruins windows and freezes desktop
A permanent workaround: Install unity-tweak-tool and disable window spread feature. This will prevent Unity from showing open windows when clicking on a launcher icon and preventing you from accidentially crashing your desktop environment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1295909 Title: Unity spread trigger ruins windows and freezes desktop Status in Compiz: Triaged Status in Unity: Confirmed Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: The latest update disabled window spreading and when triggered crashes the desktop. Everything freezes and windows cannot be switched. The only way to close an application is to shut down. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Mar 21 20:59:17 2014 DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (77 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: TOSHIBA Satellite C55-A ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-18-generic root=UUID=6b37c83b-b64c-42fc-89d3-3db46a397734 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-20 (1 days ago) dmi.bios.date: 04/12/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.10 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.10:bd04/12/2013:svnTOSHIBA:pnSatelliteC55-A:pvrPSCF6U-01Y00C:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C55-A dmi.product.version: PSCF6U-01Y00C dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 10.0.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Mar 21 18:56:33 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17223 vendor SDC xserver.version: 2:1.15.0-1ubuntu7 --- .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2014-03-19 22:45:03,298 DEBUG enabling apt cron job DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.8, 3.13.0-18-generic, x86_64: installed vboxhost, 4.3.8, 3.13.0-19-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fa20] InstallationDate: Installed on 2014-01-03 (83 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: TOSHIBA Satellit
[Touch-packages] [Bug 1293242] Re: compiz crashed with SIGSEGV in ScaleScreen::getWindows()
*** This bug is a duplicate of bug 1295909 *** https://bugs.launchpad.net/bugs/1295909 ** This bug has been marked a duplicate of bug 1295909 Unity spread trigger ruins windows and freezes desktop -- 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/1293242 Title: compiz crashed with SIGSEGV in ScaleScreen::getWindows() Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity se cerró luego de utilizar la utilidad ''Unity Tweak Tool'' especificamente al activar la opción ''Despliegue de ventanas'' Sistema actualizado, he debido reiniciar el equipo. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sun Mar 16 17:58:29 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-02-27 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140224) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0xb177dc54 <_ZNK11ScaleScreen10getWindowsEv+4>: mov0x24(%eax),%eax PC (0xb177dc54) ok source "0x24(%eax)" (0x0024) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ScaleScreen::getWindows() const () from /usr/lib/compiz/libscale.so unity::UnityScreen::OnInitiateSpread() () from /usr/lib/compiz/libunityshell.so sigc::internal::slot_call0, void>::call_it(sigc::internal::slot_rep*) () from /usr/lib/compiz/libunityshell.so sigc::internal::signal_emit0::emit(sigc::internal::signal_impl*) () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::OnScreenGrabbed() () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in ScaleScreen::getWindows() 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/unity/+bug/1293242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351308] Re: Changing language has no effect
** Description changed: broken on mako #165 Last known good image: #163 TEST CASE: 1. On a device in English, go to "System Settings/Language & Text/Display Language" 2. Scroll down the list and select another language i.e "Français (France)" 3. Tap "Confirm" ACTUAL RESULT Language did not change (the label in front of "Display language" is still English) and is still English (even after a reboot) EXPECTED LANGUAGE Setting is set to French and UI is localized after a reboot. + Same problem with the wizard. The language changes *inside* the wizard + but changes are not written to ~/.pam_environment + ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140730-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu2 Architecture: armhf Date: Fri Aug 1 15:05:35 2014 InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140801-020205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1351308 Title: Changing language has no effect Status in “accountsservice” package in Ubuntu: Confirmed Bug description: broken on mako #165 Last known good image: #163 TEST CASE: 1. On a device in English, go to "System Settings/Language & Text/Display Language" 2. Scroll down the list and select another language i.e "Français (France)" 3. Tap "Confirm" ACTUAL RESULT Language did not change (the label in front of "Display language" is still English) and is still English (even after a reboot) EXPECTED LANGUAGE Setting is set to French and UI is localized after a reboot. Same problem with the wizard. The language changes *inside* the wizard but changes are not written to ~/.pam_environment ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140730-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu2 Architecture: armhf Date: Fri Aug 1 15:05:35 2014 InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140801-020205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1351308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340154] Re: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode
I also have a system which I thought could not be upgraded beyond 12.04 because of a lack of PAE support, but then I recently found that many Pentium M CPUs can work with a PAE kernel, but do not advertise PAE support. To check whether this is the case for your system, simply install a PAE kernel: sudo apt-get install linux-generic-pae linux-headers-generic-pae See: https://help.ubuntu.com/community/EnablingPAE If you find your system really does not work with a PAE kernel, all is not lost, see: https://help.ubuntu.com/community/Lubuntu-fake-PAE I'm marking this bug as affecting modemmanager instead of modem-manager- gui. ** Changed in: modem-manager-gui (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1340154 Title: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode Status in “modem-manager-gui” package in Ubuntu: Invalid Status in “modemmanager” package in Ubuntu: New Bug description: To-date, cannot utilise Modem Manager GUI in 12.04 LTS, as it is understood that there is a 'bug' in Modem Manager version 0.5.2 that installed in Ubuntu 12.04 by default. On modem initialization it sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode. I understand the GUI works well and has been introduced into Saucy Salamander and later versions, but Modem Manager versions 0.6 or later has not yet been made available for 12.04 LTS users which enables its SMS functions etc to work. It is hoped that an updated version of Modem Manager that addresses this and other bug fixes can be introduced into 12.04 LTS very soon for users like myself who have been looking out patiently for a couple of years for this functionality. Thanks in advance for the anticipated support... cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1340154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351585] [NEW] Package version does not support "ignore-carrier" configuration option
Public bug reported: I have a couple of connections defined which are not on "auto connect" - one wired, one wireless - so that I can control which I want to be on at the same time. Since they share the same IP, leaving NetworkManager to do things automatically doesn't work since at the moment that it has both connections configured, IPv6 duplicate address detection kicks in by detecting itself and disables my IPv6 connection. Everything works fine this way normally - I just manually connect the connection I want (after disconnecting the other one first if necessary), and everything works. When I get a power cut, my switch turns off, but as a laptop my main machine effectively has a UPS. In this case, NetworkManager detects a cable disconnect on eth0, and disconnects the connection. When the power comes back on and the cable "reconnects", NetworkManager does nothing. When I'm away, this kills my connection, even after the power is restored. This breaks my expectation is that everything should be fine as long as the power cut didn't last as long as my battery. AIUI, this behaviour is by design, but more recent versions of NetworkManager have an "ignore-carrier" configuration option that is intended for my use case and would solve my problem. But Ubuntu doesn't currently ship a version that supports this. The upstream patch appears to be in http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e37935875ad84c1cdaf13b38535adc884ec188e and I see references to it for example in Red Hat's NetworkManager- config-server package. I have no idea if the upstream patch would apply cleanly and work or not. It looks like Ubuntu's delta against upstream is quite big. I don't really expect this to be fixed soon, and I'm sure I can find some kind of workaround more easily than trying to patch support in, but I thought it might be helpful to file a bug to track the existence of a real use case where a newer upstream release would be useful. ** Affects: network-manager (Ubuntu) Importance: Wishlist Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1351585 Title: Package version does not support "ignore-carrier" configuration option Status in “network-manager” package in Ubuntu: New Bug description: I have a couple of connections defined which are not on "auto connect" - one wired, one wireless - so that I can control which I want to be on at the same time. Since they share the same IP, leaving NetworkManager to do things automatically doesn't work since at the moment that it has both connections configured, IPv6 duplicate address detection kicks in by detecting itself and disables my IPv6 connection. Everything works fine this way normally - I just manually connect the connection I want (after disconnecting the other one first if necessary), and everything works. When I get a power cut, my switch turns off, but as a laptop my main machine effectively has a UPS. In this case, NetworkManager detects a cable disconnect on eth0, and disconnects the connection. When the power comes back on and the cable "reconnects", NetworkManager does nothing. When I'm away, this kills my connection, even after the power is restored. This breaks my expectation is that everything should be fine as long as the power cut didn't last as long as my battery. AIUI, this behaviour is by design, but more recent versions of NetworkManager have an "ignore-carrier" configuration option that is intended for my use case and would solve my problem. But Ubuntu doesn't currently ship a version that supports this. The upstream patch appears to be in http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e37935875ad84c1cdaf13b38535adc884ec188e and I see references to it for example in Red Hat's NetworkManager- config-server package. I have no idea if the upstream patch would apply cleanly and work or not. It looks like Ubuntu's delta against upstream is quite big. I don't really expect this to be fixed soon, and I'm sure I can find some kind of workaround more easily than trying to patch support in, but I thought it might be helpful to file a bug to track the existence of a real use case where a newer upstream release would be useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351585/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340154] Re: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode
** Also affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1340154 Title: On modem initialization, Modem Manager 0.5.2 sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode Status in “modem-manager-gui” package in Ubuntu: New Status in “modemmanager” package in Ubuntu: New Bug description: To-date, cannot utilise Modem Manager GUI in 12.04 LTS, as it is understood that there is a 'bug' in Modem Manager version 0.5.2 that installed in Ubuntu 12.04 by default. On modem initialization it sets text mode instead of PDU mode for SMS, but newer modems can't work in this mode. I understand the GUI works well and has been introduced into Saucy Salamander and later versions, but Modem Manager versions 0.6 or later has not yet been made available for 12.04 LTS users which enables its SMS functions etc to work. It is hoped that an updated version of Modem Manager that addresses this and other bug fixes can be introduced into 12.04 LTS very soon for users like myself who have been looking out patiently for a couple of years for this functionality. Thanks in advance for the anticipated support... cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1340154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351308] Re: Changing language has no effect
It's a regression in accountsservice 0.6.37-1ubuntu7 I reproduced by flashing #163 (last known good image) and upgrading: accountsservice:armhf (0.6.37-1ubuntu6, 0.6.37-1ubuntu7) libaccountsservice0:armhf (0.6.37-1ubuntu6, 0.6.37-1ubuntu7) reassigning to accountsservice ** Package changed: ubuntu-system-settings (Ubuntu) => accountsservice (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1351308 Title: Changing language has no effect Status in “accountsservice” package in Ubuntu: Confirmed Bug description: broken on mako #165 Last known good image: #163 TEST CASE: 1. On a device in English, go to "System Settings/Language & Text/Display Language" 2. Scroll down the list and select another language i.e "Français (France)" 3. Tap "Confirm" ACTUAL RESULT Language did not change (the label in front of "Display language" is still English) and is still English (even after a reboot) EXPECTED LANGUAGE Setting is set to French and UI is localized after a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140730-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu2 Architecture: armhf Date: Fri Aug 1 15:05:35 2014 InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140801-020205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1351308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351308] [NEW] Changing language has no effect
You have been subscribed to a public bug: broken on mako #165 Last known good image: #163 TEST CASE: 1. On a device in English, go to "System Settings/Language & Text/Display Language" 2. Scroll down the list and select another language i.e "Français (France)" 3. Tap "Confirm" ACTUAL RESULT Language did not change (the label in front of "Display language" is still English) and is still English (even after a reboot) EXPECTED LANGUAGE Setting is set to French and UI is localized after a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140730-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu2 Architecture: armhf Date: Fri Aug 1 15:05:35 2014 InstallationDate: Installed on 2014-08-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140801-020205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: accountsservice (Ubuntu) Importance: High Status: Confirmed ** Tags: apport-bug armhf lt-blocker lt-category-visible lt-prio-high qa-daily-testing qa-touch rtm14 utopic -- Changing language has no effect https://bugs.launchpad.net/bugs/1351308 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
Does nobody else experience this, or does nobody else have a high resolution device for being able to experience it? I get this issue also in the daily utopic unicorn (28.7.) with Unity 7.3. I believe it is due to some flexible box gtk component, but I don't have enough technical knowledge for a better guess. -- 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/1299054 Title: resizing loop on high-dpi screen Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1214352]
(In reply to comment #59) > @iveand, Bryan Berndt: Too bad you didn't read carefully the whole thread. > Anyway, here is a summary: > > - The repair dialog is an Ubuntu 12.04 specific bug, related to glib > package. See https://launchpad.net/bugs/1214352 > > The problem with KDE is another problem, mostly related to missing packages: > > - For the build from distro repositories, you should also install 'gvfs' and > 'gvfs-smb' packages for Fedora, or 'gvfs', 'gvfs-backends', > 'libreoffice-gnome' for Ubuntu. > > - For the build from libreoffice.org, you should also install 'gnome-vfs2', > 'gnome-vfs2-smb', 'ORBit2' for Fedora, or 'libgnomevfs2-0', > 'libgnomevfs2-extra', 'liborbit2'. You should also export > 'OOO_FORCE_DESKTOP=gnome', otherwise it won't work. Upgraded to LO 4.3 with the rpm's from the LO web site. (rpm -U.) Problem is recreated, as with every upgrade so far (comment 15). Most of the packages you mention were already installed. Then added the export to a KDE environment script: http://forums.opensuse.org/showthread.php/478619-LibreOffice-looks-ugly- in-SUSE-KDE ; vairation of post #3. I log into the SMB file server, and then when I double click the file I want to opem it asks to log in again, I assume that this is GVFS asking that. Once I do, then file opens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214352 Title: GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses Status in LibreOffice Productivity Suite: Confirmed Status in The "G" Library - GLib: Fix Released Status in “glib2.0” package in Ubuntu: Confirmed Bug description: On 12.04 LTS precise GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses, causing trouble down the stack in gvfs and LibreOffice (and possibly in lots of obscure bugs elsewhere). There is a patch available, but as this touches the header, it needs a full recompile of rdepends. see: https://lists.fedoraproject.org/pipermail/devel/2013-March/180302.html ff. for details To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1214352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351566] Re: Usb mouse stops working after a while (few seconds)
Dmesg File ** Attachment added: "dmesg_boot" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1351566/+attachment/4167899/+files/dmesg_boot -- 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/1351566 Title: Usb mouse stops working after a while (few seconds) Status in “xorg” package in Ubuntu: New Bug description: The optical USB mouse stops working. If I press one of the buttons it wakes up. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 2 09:53:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13bd] InstallationDate: Installed on 2014-06-13 (50 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic.efi.signed 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: 12/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA 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.:bvrUX301LAA.206:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Jul 26 10:14:39 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5126 vendor SHP xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1351566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351566] Re: Usb mouse stops working after a while (few seconds)
Dmesg file from virtual terminal with mouse stopped working (diff from dmesg_boot) ** Patch added: "dmesg.diff" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1351566/+attachment/4167900/+files/dmesg.diff -- 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/1351566 Title: Usb mouse stops working after a while (few seconds) Status in “xorg” package in Ubuntu: New Bug description: The optical USB mouse stops working. If I press one of the buttons it wakes up. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 2 09:53:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13bd] InstallationDate: Installed on 2014-06-13 (50 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic.efi.signed 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: 12/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA 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.:bvrUX301LAA.206:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Jul 26 10:14:39 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5126 vendor SHP xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1351566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351566] [NEW] Usb mouse stops working after a while (few seconds)
Public bug reported: The optical USB mouse stops working. If I press one of the buttons it wakes up. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 2 09:53:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13bd] InstallationDate: Installed on 2014-06-13 (50 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic.efi.signed 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: 12/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA 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.:bvrUX301LAA.206:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnUX301LAA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX301LAA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX301LAA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Jul 26 10:14:39 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5126 vendor SHP xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Attachment added: "Xlog file" https://bugs.launchpad.net/bugs/1351566/+attachment/4167873/+files/Xorg.0.log -- 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/1351566 Title: Usb mouse stops working after a while (few seconds) Status in “xorg” package in Ubuntu: New Bug description: The optical USB mouse stops working. If I press one of the buttons it wakes up. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 2 09:53:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13bd] InstallationDate: Installed on 2014-06-13 (50 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. UX301LAA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic.efi.signed 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: 12/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX301LAA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX301LAA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asse
[Touch-packages] [Bug 1351564] Re: chvt sometimes hangs, causing hibernation to fail
** Attachment added: "pm-suspend.log" https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1351564/+attachment/4167872/+files/pm-suspend.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1351564 Title: chvt sometimes hangs, causing hibernation to fail Status in “kbd” package in Ubuntu: New Bug description: This is probably in relation with bug #1350220, which deals with a failure in hibernation. It appears that this is caused by chvt not terminating a some points in the hibernation scripts. Yet I do not know whether the scripts or chvt are to blame. When I initiate an hibernation on my computer, the following frequently happens (about 50% of the time) : 1. screen goes black (normal) ; 2. instead of showing the progress of the writing of RAM to disk in console mode, the screen remains black ; 3. the screensaver prompt for login appears ; 4. after returning to desktop, I see that the network card is not functioning. Further debugging (PM_DEBUG=true) shows that the blocking point lies in 99video and is "chvt 63". I tried to hibernate with --quirk-no- chvt. This allows the script 99video to terminate (because it does not try a chvt 63) and the hibernation process itself to engage. However, my hibernation module, /usr/lib/pm-utils/module.d/hibernate, does a chvt 63 too, which is not controlled by the --quirk-no-chvt. So I experienced again a return to desktop with a chvt process not progressing. I killed it and hibernation took place, without any visual clue. On booting the system again, thaw took place correctly but the system was not usable because I did not get access to a console (graphical or text). Indeed, the pm-suspend.log shows that chvt 8 did not return. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: kbd 1.15.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57~ppa1-generic-tuxonice 3.13.11.4 Uname: Linux 3.13.0-32-generic-tuxonice x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 2 09:52:13 2014 InstallationDate: Installed on 2014-07-18 (14 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: kbd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1351564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351564] [NEW] chvt sometimes hangs, causing hibernation to fail
Public bug reported: This is probably in relation with bug #1350220, which deals with a failure in hibernation. It appears that this is caused by chvt not terminating a some points in the hibernation scripts. Yet I do not know whether the scripts or chvt are to blame. When I initiate an hibernation on my computer, the following frequently happens (about 50% of the time) : 1. screen goes black (normal) ; 2. instead of showing the progress of the writing of RAM to disk in console mode, the screen remains black ; 3. the screensaver prompt for login appears ; 4. after returning to desktop, I see that the network card is not functioning. Further debugging (PM_DEBUG=true) shows that the blocking point lies in 99video and is "chvt 63". I tried to hibernate with --quirk-no-chvt. This allows the script 99video to terminate (because it does not try a chvt 63) and the hibernation process itself to engage. However, my hibernation module, /usr/lib/pm-utils/module.d/hibernate, does a chvt 63 too, which is not controlled by the --quirk-no-chvt. So I experienced again a return to desktop with a chvt process not progressing. I killed it and hibernation took place, without any visual clue. On booting the system again, thaw took place correctly but the system was not usable because I did not get access to a console (graphical or text). Indeed, the pm-suspend.log shows that chvt 8 did not return. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: kbd 1.15.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57~ppa1-generic-tuxonice 3.13.11.4 Uname: Linux 3.13.0-32-generic-tuxonice x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 2 09:52:13 2014 InstallationDate: Installed on 2014-07-18 (14 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: kbd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kbd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1351564 Title: chvt sometimes hangs, causing hibernation to fail Status in “kbd” package in Ubuntu: New Bug description: This is probably in relation with bug #1350220, which deals with a failure in hibernation. It appears that this is caused by chvt not terminating a some points in the hibernation scripts. Yet I do not know whether the scripts or chvt are to blame. When I initiate an hibernation on my computer, the following frequently happens (about 50% of the time) : 1. screen goes black (normal) ; 2. instead of showing the progress of the writing of RAM to disk in console mode, the screen remains black ; 3. the screensaver prompt for login appears ; 4. after returning to desktop, I see that the network card is not functioning. Further debugging (PM_DEBUG=true) shows that the blocking point lies in 99video and is "chvt 63". I tried to hibernate with --quirk-no- chvt. This allows the script 99video to terminate (because it does not try a chvt 63) and the hibernation process itself to engage. However, my hibernation module, /usr/lib/pm-utils/module.d/hibernate, does a chvt 63 too, which is not controlled by the --quirk-no-chvt. So I experienced again a return to desktop with a chvt process not progressing. I killed it and hibernation took place, without any visual clue. On booting the system again, thaw took place correctly but the system was not usable because I did not get access to a console (graphical or text). Indeed, the pm-suspend.log shows that chvt 8 did not return. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: kbd 1.15.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57~ppa1-generic-tuxonice 3.13.11.4 Uname: Linux 3.13.0-32-generic-tuxonice x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 2 09:52:13 2014 InstallationDate: Installed on 2014-07-18 (14 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: kbd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1351564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350220] Re: hibernation fails because chvt 63 hangs
** Description changed: + EDIT : initial title was "hibernation fails because 99video does not + terminate" + When I initiate an hibernation on my computer, the following frequently happens (about 50% of the time) : 1. screen goes black (normal) ; 2. instead of showing the progress of the writing of RAM to disk in console mode, the screen remains black ; 3. the screensaver prompt for login appears ; 4. after returning to desktop, I see that the network card is not functioning ; 5. /var/log/pm-suspend.log last line is "Running hook /usr/lib/pm-utils/sleep.d/99video hibernate hibernate:". Indeed, a ps -ef | grep 99video shows that the /usr/lib/pm- utils/sleep.d/99video script is still running. If I kill this script, pm-utils logs "/usr/lib/pm-utils/sleep.d/99video hibernate hibernate: Returned exit code 143.", aborts hibernation and then runs the hooks for thaw. I can then try again to hibernate, and it works : I never had this bug trigger twice in a row. This bug did not occur when I was running Ubuntu 12.04 and the corresponding kernels (but back then I was also using the video card driver from AMD's website instead of fglrx-updates). + + EDIT : further debugging (PM_DEBUG=true) shows that the blocking point in 99video is "chvt 63". I tried to hibernate with --quirk-no-chvt. This allows the script 99video to terminate and the hibernation process itself to engage. However, my hibernation module, /usr/lib/pm-utils/module.d/hibernate, does a chvt 63 too, which is not controlled by the --quirk-no-chvt. + + So I experienced again a return to desktop with a chvt process not + progressing. I killed it and hibernation took place, without any visual + clue. On booting the system again, thaw took place correctly but the + system was not usable because I did not get access to a console + (graphical or text). Indeed, the pm-suspend.log shows that chvt 8 did + not return. + ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-32.57~ppa1-generic-tuxonice 3.13.11.4 Uname: Linux 3.13.0-32-generic-tuxonice x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jul 30 08:47:17 2014 InstallationDate: Installed on 2014-07-18 (11 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - hibernation fails because chvt 63 hangs + hibernation fails because chvt hangs ** Attachment added: "log with debugging and --quirk-no-chvt" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1350220/+attachment/4167863/+files/pm-suspend.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1350220 Title: hibernation fails because chvt hangs Status in “pm-utils” package in Ubuntu: New Bug description: EDIT : initial title was "hibernation fails because 99video does not terminate" When I initiate an hibernation on my computer, the following frequently happens (about 50% of the time) : 1. screen goes black (normal) ; 2. instead of showing the progress of the writing of RAM to disk in console mode, the screen remains black ; 3. the screensaver prompt for login appears ; 4. after returning to desktop, I see that the network card is not functioning ; 5. /var/log/pm-suspend.log last line is "Running hook /usr/lib/pm-utils/sleep.d/99video hibernate hibernate:". Indeed, a ps -ef | grep 99video shows that the /usr/lib/pm- utils/sleep.d/99video script is still running. If I kill this script, pm-utils logs "/usr/lib/pm- utils/sleep.d/99video hibernate hibernate: Returned exit code 143.", aborts hibernation and then runs the hooks for thaw. I can then try again to hibernate, and it works : I never had this bug trigger twice in a row. This bug did not occur when I was running Ubuntu 12.04 and the corresponding kernels (but back then I was also using the video card driver from AMD's website instead of fglrx-updates). EDIT : further debugging (PM_DEBUG=true) shows that the blocking point in 99video is "chvt 63". I tried to hibernate with --quirk-no-chvt. This allows the script 99video to terminate and the hibernation process itself to engage. However, my hibernation module, /usr/lib/pm-utils/module.d/hibernate, does a chvt 63 too, which is not controlled by the --quirk-no-chvt. So I experienced again a return to desktop with a chvt process not progressing. I killed it and hibernation took place, without any visual clue. On booting the system again, thaw took place correctly but the system was not usable because I did not get access to a console (graphical or text). Indeed
[Touch-packages] [Bug 1350220] Re: hibernation fails because chvt 63 hangs
** Summary changed: - hibernation fails because 99video does not terminate + hibernation fails because chvt 63 hangs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1350220 Title: hibernation fails because chvt 63 hangs Status in “pm-utils” package in Ubuntu: New Bug description: When I initiate an hibernation on my computer, the following frequently happens (about 50% of the time) : 1. screen goes black (normal) ; 2. instead of showing the progress of the writing of RAM to disk in console mode, the screen remains black ; 3. the screensaver prompt for login appears ; 4. after returning to desktop, I see that the network card is not functioning ; 5. /var/log/pm-suspend.log last line is "Running hook /usr/lib/pm-utils/sleep.d/99video hibernate hibernate:". Indeed, a ps -ef | grep 99video shows that the /usr/lib/pm- utils/sleep.d/99video script is still running. If I kill this script, pm-utils logs "/usr/lib/pm- utils/sleep.d/99video hibernate hibernate: Returned exit code 143.", aborts hibernation and then runs the hooks for thaw. I can then try again to hibernate, and it works : I never had this bug trigger twice in a row. This bug did not occur when I was running Ubuntu 12.04 and the corresponding kernels (but back then I was also using the video card driver from AMD's website instead of fglrx-updates). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-32.57~ppa1-generic-tuxonice 3.13.11.4 Uname: Linux 3.13.0-32-generic-tuxonice x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jul 30 08:47:17 2014 InstallationDate: Installed on 2014-07-18 (11 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1350220/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348365] Re: MTP should not respond to new connection requests if the screen is locked
** Changed in: mtp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1348365 Title: MTP should not respond to new connection requests if the screen is locked Status in “mtp” package in Ubuntu: Confirmed Bug description: Ubuntu Touch will soon have/now has the ability to set a PIN/password for the user. If the password is set and the screen is locked, MTP should not respond to new connection requests per Phone Delivery requirements. This is needed for RTM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1348365/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"
Hi, seems I get the same bug in 14.04 Suspend works, but not after shutdown. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/324295 Title: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p" Status in “sysvinit” package in Ubuntu: Confirmed Bug description: Binary package hint: upstart I am not sure whether this is the fault of upstart, or some other package, but the problem is: Wake-on-LAN works in the following situations: 1) when suspending the system to S3 (using pm-suspend) 2) When issuing "sudo halt -p" from the command line. Note: I have not tested WOL from hibernate If I shut down the system from XFCE or by issuing "sudo shutdown -h now" I cannot wake up my system by sending a WOL packet from another computer. I really want to avoid using suspend as suspend support seems a bit unstable on my computer running as a mythbackend. I also understand that "halt -p" does not run the shutdown scripts in rc0, rc1 and rc6 which probably is not good for my system services. But it seems like that somewhere during the shutdown scripts WOL is disabled. I have tried setting NETDOWN=no in /etc/init.d/halt to prevent halt from bringing the network interfaces down. I enable WOL with a script in init.d, here is the script: #!/bin/sh ### BEGIN INIT INFO # Provides: wakeonlanconfig # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 S # Default-Stop: 1 6 # Short-Description: Set up Wake On Lan ### END INIT INFO ETHTOOL="/usr/sbin/ethtool" DEV="eth1" case "$1" in start) echo -n "Setting $DEV to wakeonlan..." $ETHTOOL -s $DEV wol g; echo " done.";; stop) ;; esac exit 0 The Wakeonlan script is run at the following runlevels: locate wakeonlan /etc/init.d/wakeonlanconfig /etc/rc0.d/K20wakeonlanconfig /etc/rc1.d/K20wakeonlanconfig /etc/rc2.d/S20wakeonlanconfig /etc/rc3.d/S20wakeonlanconfig /etc/rc4.d/S20wakeonlanconfig /etc/rc5.d/S20wakeonlanconfig /etc/rc6.d/K20wakeonlanconfig /etc/rcS.d/S20wakeonlanconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/324295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 324295] Re: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sysvinit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/324295 Title: WOL does not work when using shutdown, but works with suspend (S3) and "halt -p" Status in “sysvinit” package in Ubuntu: Confirmed Bug description: Binary package hint: upstart I am not sure whether this is the fault of upstart, or some other package, but the problem is: Wake-on-LAN works in the following situations: 1) when suspending the system to S3 (using pm-suspend) 2) When issuing "sudo halt -p" from the command line. Note: I have not tested WOL from hibernate If I shut down the system from XFCE or by issuing "sudo shutdown -h now" I cannot wake up my system by sending a WOL packet from another computer. I really want to avoid using suspend as suspend support seems a bit unstable on my computer running as a mythbackend. I also understand that "halt -p" does not run the shutdown scripts in rc0, rc1 and rc6 which probably is not good for my system services. But it seems like that somewhere during the shutdown scripts WOL is disabled. I have tried setting NETDOWN=no in /etc/init.d/halt to prevent halt from bringing the network interfaces down. I enable WOL with a script in init.d, here is the script: #!/bin/sh ### BEGIN INIT INFO # Provides: wakeonlanconfig # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 S # Default-Stop: 1 6 # Short-Description: Set up Wake On Lan ### END INIT INFO ETHTOOL="/usr/sbin/ethtool" DEV="eth1" case "$1" in start) echo -n "Setting $DEV to wakeonlan..." $ETHTOOL -s $DEV wol g; echo " done.";; stop) ;; esac exit 0 The Wakeonlan script is run at the following runlevels: locate wakeonlan /etc/init.d/wakeonlanconfig /etc/rc0.d/K20wakeonlanconfig /etc/rc1.d/K20wakeonlanconfig /etc/rc2.d/S20wakeonlanconfig /etc/rc3.d/S20wakeonlanconfig /etc/rc4.d/S20wakeonlanconfig /etc/rc5.d/S20wakeonlanconfig /etc/rc6.d/K20wakeonlanconfig /etc/rcS.d/S20wakeonlanconfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/324295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp