[Touch-packages] [Bug 1348890] Re: [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN
All required logs in attachment files. When evtest running and Fn+F5 or Fn+F6 is pressed nothing happening. But I can adjust brightness through Right Click on Battery Icon -> Power Settings -> screen brightness by moving slide bar. ** Attachment added: "Logs" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1348890/+attachment/4168570/+files/asusf5f6_evtest_dmi_id_logs.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1348890 Title: [keymap] Brightness keys Fn+F5 and Fn+F6 don't work for Asus UX32LN Status in “systemd” package in Ubuntu: Incomplete Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1348890/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: manager crash: GLib-GObject-CRITICAL (ubutu 13)
** Also affects: modem-manager-gui (Ubuntu) Importance: Undecided Status: New ** Changed in: modemmanager (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/1351814 Title: manager crash: GLib-GObject-CRITICAL (ubutu 13) Status in “modem-manager-gui” package in Ubuntu: New Status in “modemmanager” package in Ubuntu: Invalid 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/modem-manager-gui/+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 1313996] Re: [MIR] Tracker
Didier, - COPYING.LGPL is fixed upstream and will be included in the next stable release (although I can cherry-pick the patches if you prefer) - rpath is now fixed via --enable-new-dtags, will be upstreamed soon https://bugzilla.gnome.org/show_bug.cgi?id=733857 - I hooked up unit tests to run under autopkgtest (they really can't run at build time since they use the tracker dbus api etc). - I haven't enabled functional tests yet, there is some upstream work in progress to get these running, so will wait and see how that pans out. - debian/shlibs.local: as far as I can tell this is correct and doesn't contain any obsolete libraries. ** Bug watch added: GNOME Bug Tracker #733857 https://bugzilla.gnome.org/show_bug.cgi?id=733857 ** Changed in: tracker (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) -- 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/1313996 Title: [MIR] Tracker Status in Ubuntu GNOME: New Status in “tracker” package in Ubuntu: Incomplete Bug description: Availability: Currently in universe, builds on all arches. Consists of a trivial diff from the debian packaging. Rationale: Nautilus has an optional tracker module which provides indexing and system file search. Currently this is disabled since tracker is in universe and nautilus in main. This provides a core functionally for the GNOME desktop, in that file searching from the overview only works if nautilus is built with the tracker module. Quality Assurance: Package does not require configuration, and does not ask any debconf questions. It is well supported upstream with the stable tracker 1.0 release having been made recently (which will sync from debian this cycle) Security: No know CVE's UI Standards: The only GUI part is completely option and a Suggests. Tracker is largely integrated into the various GNOME components Dependencies: All dependencies are in Main already Standards Compliance: currently compliant with 3.9.4 Maintenance: Ubuntu GNOME team will provide maintenance beyond what is required after merging debian packages etc. Additional Info: tracker is only seeded on Ubuntu GNOME. building nautilus with tracker support would add libtracker-sparql-0.16-0 to the other desktop seeds. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: tracker 1.0.0-1ubuntu1~trusty1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Apr 29 12:39:58 2014 InstallationDate: Installed on 2012-09-23 (583 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1313996/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: no sound
You've installed AMD's proprietary fglrx/Catalyst driver and it no longer supports your card. Follow this procedure to restore the open- source radeon driver: http://wiki.cchtml.com/index.php/Ubuntu_Trusty_Installation_Guide#Removing_Catalyst.2Ffglrx As for audio issue, please file a new bug, using the following command to gather audio info/logs automatically: ubuntu-bug audio ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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: Invalid 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-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1351656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351868] [NEW] tracker-miner-fs crashed with SIGSEGV in g_main_context_dispatch()
Public bug reported: apport reported that ** Affects: tracker (Ubuntu) Importance: Undecided Status: New -- 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/1351868 Title: tracker-miner-fs crashed with SIGSEGV in g_main_context_dispatch() Status in “tracker” package in Ubuntu: New Bug description: apport reported that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1351868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1285783] Re: Right panel has a transparent background
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1285783 Title: Right panel has a transparent background Status in “gtk+3.0” package in Ubuntu: Confirmed Status in “ubuntu-themes” package in Ubuntu: Fix Committed Bug description: Launching gnome-tweak-tool and choosing a category on the left panel makes the right panel transparent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1285783/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Thanks for that! This has to wait until we acutally land 214, or we find a way to provide both APIs. ** Changed in: systemd-shim (Ubuntu) Status: New => Triaged -- 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: Triaged 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 1351566] Re: Usb mouse stops working after a while (few seconds)
It works with kernel 3.13.0-32-generic ** Changed in: xorg (Ubuntu) Status: New => Fix Released -- 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: Fix Released 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 1351814] Re: manager crash: GLib-GObject-CRITICAL (ubutu 13)
** Also affects: modem-manager-gui 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 Modem Manager Gui: New Status in “modem-manager-gui” package in Ubuntu: New Status in “modemmanager” package in Ubuntu: Invalid 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/modem-manager-gui/+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
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_via.c?id=5a6f294e87974e6ec68d7113553ffd975d83bf15 you may need to ask the author whether you case is related to this patch -- 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 1252733] Re: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume
I tried installing the daily drivers but the white noice is still there for me with PCI SSID 1028:060a. The output from alsa-info is here: http://www.alsa- project.org/db/?f=b99f1bc40f3786717ae49bf780a8ddd75831cac6 This was with the latest updates on 14.04 and oem-audio-hda-daily- dkms_0.201407291531~ubuntu14.04.1_all.deb. Any ideas for how to fix the issue would be appreciated. -- 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/1252733 Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: When listening to sound on my laptop through headphones, there's a constant background hiss (which disappears only when all sound has been stopped for a few seconds. power saving I guess). I also need to turn the volume *way* down to 10% for the sound volume to be reasonable (it's way too loud otherwise). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: martijn2130 F pulseaudio /dev/snd/pcmC1D0p: martijn2130 F...m pulseaudio /dev/snd/controlC0: martijn2130 F pulseaudio Date: Tue Nov 19 14:26:46 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-13 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Intern geluid - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/24/2013:svnDellInc.:pnXPS12-9Q33:pvrA03:rvnDellInc.:rnXPS12-9Q33:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1252733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351879] [NEW] There is no @ key on default LTE 14.04.1 install with hungarian keyboard
Public bug reported:
With hungarian keyboard layout there is a problem some ALTGR+key combination
like ALTGR+v (@), ALTGR+b ({) and so on. The problem occur with any interface I
use in X (terminal, browser, editor). There is no way to get work ALTRGR
correctly.
I tried to do suggestions in
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1284635 by
https://launchpad.net/~agent-ryan (go to "Preferences → Language Suport" and on
"Language" tab set "Keyboard input method system" to "none". Then reboot
system).
It doesn't solve the problem.
** Affects: ibus (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- With hungarian keyboard layout there is a problem some ALTGR+key combination
like ALTGR+v (@), ALTGR+b ({) and so on. the problem is that any interface i
use in X (terminal, browser, editor) there are no way to get work ALTRGR
correctly.
- I tried to do suggestions in
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1284635 by
https://launchpad.net/~agent-ryan (go to "Preferences → Language Suport" and on
"Language" tab set "Keyboard input method system" to "none". Then reboot
system).
- I doesn't solve the problem.
+ With hungarian keyboard layout there is a problem some ALTGR+key combination
like ALTGR+v (@), ALTGR+b ({) and so on. The problem occur with any interface I
use in X (terminal, browser, editor). There is no way to get work ALTRGR
correctly.
+ I tried to do suggestions in
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1284635 by
https://launchpad.net/~agent-ryan (go to "Preferences → Language Suport" and on
"Language" tab set "Keyboard input method system" to "none". Then reboot
system).
+ It doesn't solve the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1351879
Title:
There is no @ key on default LTE 14.04.1 install with hungarian
keyboard
Status in “ibus” package in Ubuntu:
New
Bug description:
With hungarian keyboard layout there is a problem some ALTGR+key combination
like ALTGR+v (@), ALTGR+b ({) and so on. The problem occur with any interface I
use in X (terminal, browser, editor). There is no way to get work ALTRGR
correctly.
I tried to do suggestions in
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1284635 by
https://launchpad.net/~agent-ryan (go to "Preferences → Language Suport" and on
"Language" tab set "Keyboard input method system" to "none". Then reboot
system).
It doesn't solve the problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1351879/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1252733] Re: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume
Sorry, I was a bit too quick in posting that. When adding the line “options snd-hda-intel model=dell-headset-multi" to /etc/modprobe.d /alsa-base.conf it now seems to work without noise with the daily drivers! Thanks for the good work! -- 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/1252733 Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: When listening to sound on my laptop through headphones, there's a constant background hiss (which disappears only when all sound has been stopped for a few seconds. power saving I guess). I also need to turn the volume *way* down to 10% for the sound volume to be reasonable (it's way too loud otherwise). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: martijn2130 F pulseaudio /dev/snd/pcmC1D0p: martijn2130 F...m pulseaudio /dev/snd/controlC0: martijn2130 F pulseaudio Date: Tue Nov 19 14:26:46 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-13 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Intern geluid - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/24/2013:svnDellInc.:pnXPS12-9Q33:pvrA03:rvnDellInc.:rnXPS12-9Q33:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1252733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301015] Re: Networking does not restart
Same problem here.
As mentioned by others, ifup/down it's not a real solution to restart
interfaces (all interfaces), and it's strange to not have a real error
message on stout.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1301015
Title:
Networking does not restart
Status in “ifupdown” package in Ubuntu:
Opinion
Bug description:
In Ubuntu Server 14.04 it appears it is not possible to restart
networking. This is fresh install from ISO.
wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
wirehive@ubuntu:~$ echo $?
1
wirehive@ubuntu:~$ sudo service networking restart
stop: Job failed while stopping
start: Job is already running: networking
wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
+ PATH=/sbin:/bin
+ RUN_DIR=/run/network
+ IFSTATE=/run/network/ifstate
+ STATEDIR=/run/network/state
+ '[' -x /sbin/ifup ']'
+ '[' -x /sbin/ifdown ']'
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
++ . /lib/lsb/init-functions.d/50-ubuntu-logging
+++ LOG_DAEMON_MSG=
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ CONFIGURE_INTERFACES=yes
+ EXCLUDE_INTERFACES=
+ VERBOSE=no
+ '[' -f /etc/default/networking ']'
+ verbose=
+ '[' no = yes ']'
+ case "$1" in
+ init_is_upstart
+ '[' -x /sbin/initctl ']'
+ /bin/grep -q upstart
+ /sbin/initctl version
+ return 0
+ exit 1
wirehive@ubuntu:~$ sudo bash -x service networking restart
++ basename service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename service
+ USAGE='Usage: service < option > | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case "${1}" in
+ '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
+ '[' 2 -eq 2 -a restart = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=networking
+ shift
+ '[' 1 -gt 0 ']'
+ case "${1}" in
+ '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z networking ']'
+ '[' -z '' ']'
+ ACTION=restart
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/networking.conf ']'
+ which initctl
+ grep -q upstart
+ initctl version
+ case "${ACTION}" in
+ stop networking
stop: Job failed while stopping
+ :
+ exec start networking
start: Job is already running: networking
wirehive@ubuntu:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351903] [NEW] network-manager-gnome 0.9.8.8-0ubuntu4.3 & or associated libraries cause HUGE memory usage on wlan0
Public bug reported: Network-manager-gnome 0.9.8.8-0ubuntu4.3 & associated libraries cause HUGE memory usage on wlan0. Usage of wlan0 by any net app causes resident memory consumption by NMG to grow until all system memory is used and system becomes unresponsive. Reverting to previous version of NMG (0.9.8.8-0ubuntu4.2) eliminates the issue and fucntions as expected. Xubuntu 14.04 LTS up-to-date AMD64 Toshiba CD560 Laptop ** Affects: network-manager (Ubuntu) Importance: Undecided 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/1351903 Title: network-manager-gnome 0.9.8.8-0ubuntu4.3 & or associated libraries cause HUGE memory usage on wlan0 Status in “network-manager” package in Ubuntu: New Bug description: Network-manager-gnome 0.9.8.8-0ubuntu4.3 & associated libraries cause HUGE memory usage on wlan0. Usage of wlan0 by any net app causes resident memory consumption by NMG to grow until all system memory is used and system becomes unresponsive. Reverting to previous version of NMG (0.9.8.8-0ubuntu4.2) eliminates the issue and fucntions as expected. Xubuntu 14.04 LTS up-to-date AMD64 Toshiba CD560 Laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
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/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner Status in Unity: New Status in “mediascanner” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I just noticed that ~/.cache/upstart/ folder on my computer is taking up 69GB of space. Upon further investigation, I found out that mediascanner.log and unity-panel-service.log take 12GB and 54GB of space respectively. I'm not entirely sure if this is related to upstart as I had removed logrotate package because of a conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
attached dmesg output for degraded boot up to premount ** Attachment added: "dmesg_upto_premount_degraded.txt" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+attachment/4168673/+files/dmesg_upto_premount_degraded.txt -- 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 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
This isn't limited to Unity. Just found my start-kde.log had swollen to several gigabytes because of a V4L bug that VLC had been spewing out for several minutes. Upstart needs to be more clever about repeated messages. syslog can, for example, munch quick duplicates and say "Line repeated x times" -- 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/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner Status in Unity: New Status in “mediascanner” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I just noticed that ~/.cache/upstart/ folder on my computer is taking up 69GB of space. Upon further investigation, I found out that mediascanner.log and unity-panel-service.log take 12GB and 54GB of space respectively. I'm not entirely sure if this is related to upstart as I had removed logrotate package because of a conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
The primary difference that I see for degraded boot is this error just ahead of activating volume group 'dataone' 'watershed sh -c '/sbin/lvm vgscan; /sbin/lvm vgchange -a y''(err) ' device-mapper: reload ioctl on failed: Invalid argument' and also after that point the 55-dm and 56-lvm rules do not fire and create the device setup like what happens in the _normal.txt log. If anyone does compare these logs you can search for the volume group name 'dataone' on both files to see what I am referring to. -- 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 1351528] Re: boot fails on degraded raid (mdraid) due to LVM root (combined / + /boot) missing device tables at mount time
attached dmesg output for normal boot up to premount ** Attachment added: "dmesg_upto_premount_normal.txt" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+attachment/4168674/+files/dmesg_upto_premount_normal.txt -- 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 1351916] [NEW] 4-pin jack mic doesn't work
Public bug reported: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: 4-pin audio mic -- 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/1351916 Title: 4-pin jack mic doesn't work Status in “pulseaudio” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351916] Re: 4-pin jack mic doesn't work
** Description changed: - I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). + I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. + EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. -- 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/1351916 Title: 4-pin jack mic doesn't work Status in “pulseaudio” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: manager crash: GLib-GObject-CRITICAL (ubutu 13)
Please run this command in a terminal: "apport-collect 1351814" to add missing system information to this bug report. ** Changed in: modem-manager-gui (Ubuntu) Status: New => Incomplete -- 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 Modem Manager Gui: New Status in “modem-manager-gui” package in Ubuntu: Incomplete Status in “modemmanager” package in Ubuntu: Invalid 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/modem-manager-gui/+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 1351814] Re: manager crash: GLib-GObject-CRITICAL (ubutu 13)
Did you get a dialog that asked to report the issue when this happened? It could also be helpful if you could install this package "libglib2.0-0-dbg" and then update the error message above. -- 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 Modem Manager Gui: New Status in “modem-manager-gui” package in Ubuntu: Incomplete Status in “modemmanager” package in Ubuntu: Invalid 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/modem-manager-gui/+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 1312282] Re: wifi fails to connect after resuming from sleep
*** This bug is a duplicate of bug 1286552 *** https://bugs.launchpad.net/bugs/1286552 ** This bug has been marked a duplicate of bug 1286552 No wifi after suspend -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1312282 Title: wifi fails to connect after resuming from sleep Status in “wpa” package in Ubuntu: New Bug description: wifi will successfully connect after resuming from sleep if process wpa_supplicant is killed. problem began after upgrading from ubuntu 13.10 to 14.4. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Thu Apr 24 12:13:25 2014 ExecutablePath: /sbin/wpa_supplicant InstallationDate: Installed on 2013-09-17 (218 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcEnviron: SourcePackage: wpa UpgradeStatus: Upgraded to trusty on 2014-04-18 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1312282/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Changed in: modemmanager (Ubuntu) Status: New => Incomplete -- 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: Incomplete 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 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
Please find or report this bug upstream first: https://bugzilla.gnome.org/browse.cgi?product=NetworkManager Or see bug #1076981 and bug #1351935 to backport a newer modem manager to 12.04 LTS. -- 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: Incomplete 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 1351814] Re: manager crash: GLib-GObject-CRITICAL (ubutu 13)
apport information ** Tags added: apport-collected saucy ** Description changed: 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 :/. + PD: the first time it works fine, but I restart the computer and not work more :/. + --- + ApportVersion: 2.12.5-0ubuntu2.2 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + InstallationDate: Installed on 2013-06-02 (427 days ago) + InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) + MarkForUpload: True + Package: modem-manager-gui 0.0.16-2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 + Tags: saucy + Uname: Linux 3.11.0-26-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2014-08-01 (2 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1351814/+attachment/4168690/+files/Dependencies.txt -- 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 Modem Manager Gui: New Status in “modem-manager-gui” package in Ubuntu: Incomplete Status in “modemmanager” package in Ubuntu: Invalid 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 :/. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-06-02 (427 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True Package: modem-manager-gui 0.0.16-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Tags: saucy Uname: Linux 3.11.0-26-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-08-01 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+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 1351814] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1351814/+attachment/4168691/+files/ProcEnviron.txt -- 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 Modem Manager Gui: New Status in “modem-manager-gui” package in Ubuntu: Incomplete Status in “modemmanager” package in Ubuntu: Invalid 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 :/. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-06-02 (427 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True Package: modem-manager-gui 0.0.16-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Tags: saucy Uname: Linux 3.11.0-26-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-08-01 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+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 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
** Description changed: - 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. + 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! + + See also bug report upstream in modem manager GUI: + http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?15.item.3.3.0 -- 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: Incomplete 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! See also bug report upstream in modem manager GUI: http://linuxonly.ru/cms/e107_plugins/bug_tracker/bugs.php?15.item.3.3.0 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 1351227]
Reproduced with the head of the coming backports branch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1351227 Title: libwebp ftbfs on arm64 Status in The GNU Compiler Collection: Unknown Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “libwebp” package in Ubuntu: Confirmed Bug description: ICE To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1351227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351227] Re: libwebp ftbfs on arm64
** Changed in: gcc Status: New => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1351227 Title: libwebp ftbfs on arm64 Status in The GNU Compiler Collection: Unknown Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “libwebp” package in Ubuntu: Confirmed Bug description: ICE To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1351227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
I have been having an issue like this for a little over a week now. Oddly coinciding with when one of my ram sticks crapped out it could be that for whatever reason my previous ram total of 4gb was compensating and the problem could be older than i am aware of, in any case it seems the only time it happens for me is when i am running flash applications in chromium. Kill the hud and all comes back to normal. If i don't catch it early enough then my system becomes virtually unusable so much so that i cant even get up the system monitor to kill the service. As with others, it seems that as long as i dont have other applications running then i can scrape by with my browsing etc. 14.04LTS (daily updated) x64 2GB ram -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/li
[Touch-packages] [Bug 721982] Re: Corrupt display for history search in vi-mode, 256-color prompt
should be fixed in 4.3, in 14.04 LTS
** Changed in: bash (Ubuntu)
Status: Confirmed => Fix Released
--
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/721982
Title:
Corrupt display for history search in vi-mode, 256-color prompt
Status in “bash” package in Ubuntu:
Fix Released
Status in “readline6” package in Ubuntu:
Fix Released
Status in “bash” package in Debian:
New
Status in “readline6” package in Debian:
Fix Released
Bug description:
Binary package hint: bash
This is on Ubuntu 10.10. It very likely still remains in Natty.
I use bash with a prompt that is derived from the current backgrounded
jobs (the script I use to do this is at
http://micah.cowan.name/hg/promptjobs/ - you just source the file and
it does everything). I've customized the colors used, to take
advantage of 256-color support in gnome-terminal. An instance of the
prompt that might be produced is:
PS1="\[\033[m\017\033[38;5;103m\]micah-
acer\[\033[1m\033[38;5;19m\](\[\033[m\017\033[38;5;83m\]\061\[\033[m\017\033[38;5;189m\]wtitle\[\033[1m\033[38;5;19m\])\[\033[m\017\033[m\017\033[38;5;103m\]$
\[\033[m\017\]"
(This prompt will only display correctly in xterm-compatible
terminals; the term I use is gnome-terminal.)
With a prompt like this, and in vi-mode ("set -o vi" in bash),
attempting to initiate a search in the history, results in display
glitches (specifically, the history line bash/readline jumps to is
displayed far over to the right, and with a couple garbage characters
before it).
Steps to reproduce:
1. Be in vi-mode ("set -o vi" in bash): in particular, readline's
"non-incremental-reverse-search-history" MUST be bound to the "/" key, as this
has significant effects on how bash/readline choose to prompt for a history
search string (even though, for me at least, the "bind" command doesn't seem to
reflect this). If you're running these steps, it would be advisible for you to
be sufficiently familiar with vi-style bindings to know how to enter commands.
2. Set PS1 as described above.
3. Invoke the non-incremental-reverse-search-history function by pressing ESC
(to escape vi's insert-mode) and "/" (to prompt for reverse history).
4. At this point, the "/" you just typed may not be showing up properly: this
is the first symptom that something's wrong.
5. Type in some string that should be present in your recent bash history (so
that bash will jump to a different line), and hit enter.
Result:
The history line bash jumps to will be drawn in the wrong location (far right
of the prompt), and with garbage characters; typing "k" or "j" (or the cursor
keys) to move up or down in history continues to draw these lines in the wrong
location.
Expected Result:
The jumped-to line ought to be drawn immediately to the right of the prompt,
and without garbage characters before it.
Cause of bug:
This bug is from readline (it is present both in the readline6 source package
(and probably older, such as readline5), and bash's own built-in readline code
(which has few differences from the sources in readline6). The bug lies in the
function rl_message in display.c, which is called by _rl_nsearch_init, which is
called from noninc_search. rl_message is primarily intended for writing a
"message" on the current line, which doesn't normally include "invisible"
characters (escape sequences, like the one I'm using in my prompt to set
advanced colors), but in this case is being (ab)used to include the prompt. It
uses a buffer of only 128 characters, which in the case of the above
prompt/PS1, is overrun. As long as the system library provides vsnprintf, this
does not lead to a potential buffer overflow, but the results are truncated,
and this is the source of the graphical display glitch, because (a) the prompt
is truncated in the middle of a sequence of "invisible" characters, and (b) I
think the readline code may have other bugs that cause character-counting not
to work properly if the prompt itself is not completely present at the
beginning of a buffer whose value is derived from the result of rl_message.
Solution:
rl_message ought to use a dynamically-allocated buffer instead, so it can
adjust the size as needed. I'll attach a patch to provide this shortly.
Workaround:
The statically-allocated buffer is only used to store the final line in a
multi-line prompt (including any invisible characters, and the special codes
used by readline to mark the start and end of invisible-character sequences).
Thus, if you add a newline in the prompt just before the "\$ ", the static
buffer should have plenty of room. Similar methods might include not using 256
color support, or any other means to shorten the total size of the prompt
string below 127.
I'll attach a patch that implements the described solution
momentarily.
[Touch-packages] [Bug 387456] Re: wrong mtu value on dsl connection
I am seeing this behaviour in 14.04. MTU set to 1392 in GUI, but ifconfig displays 1492. -- 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/387456 Title: wrong mtu value on dsl connection Status in NetworkManager: Expired Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager i am using pppoe connection for internet. however, i cant visit some sites and i cannot use pidgin for msn on 9.04 due to wrong mtu value for ppp0. network manager sets 1492 as mtu value for dsl connections. if i use pppoeconf instead of network manager to set my connection, it gives 1488 and everything works as expected. i am now manually setting mtu with ifconfig ppp0 mtu 1488 everytime a make a connection. and also trying to set the mtu value for my dsl connection with the gui of network-manager does not work, and it gives 1492 all time. this was not a problem with 8.10, and i am not the only person affected on my network. network-manager: Installed: 0.7.1~rc4.1.cf199a964-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/387456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1247574] Re: There is no remote graphical login tool
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/1247574 Title: There is no remote graphical login tool Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Hello, I tried to find a working solution for remote graphical login to Ubuntu 13.10. Found nothing working. For me, this kind of features won't let us fix the bug #1. While there are options for remote connection to the active session, remote login is something hard to establish. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1247574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 387456] Re: wrong mtu value on dsl connection
Editing the file /etc/NetworkManager/system-connections/ and adding the section below seems to work around the issue: [ppp] mtu=1392 mru=1392 -- 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/387456 Title: wrong mtu value on dsl connection Status in NetworkManager: Expired Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager i am using pppoe connection for internet. however, i cant visit some sites and i cannot use pidgin for msn on 9.04 due to wrong mtu value for ppp0. network manager sets 1492 as mtu value for dsl connections. if i use pppoeconf instead of network manager to set my connection, it gives 1488 and everything works as expected. i am now manually setting mtu with ifconfig ppp0 mtu 1488 everytime a make a connection. and also trying to set the mtu value for my dsl connection with the gui of network-manager does not work, and it gives 1492 all time. this was not a problem with 8.10, and i am not the only person affected on my network. network-manager: Installed: 0.7.1~rc4.1.cf199a964-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/387456/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: manager crash: GLib-GObject-CRITICAL (ubutu 13)
** Changed in: modem-manager-gui Status: New => Confirmed -- 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 Modem Manager Gui: Confirmed Status in “modem-manager-gui” package in Ubuntu: Incomplete Status in “modemmanager” package in Ubuntu: Invalid 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 :/. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-06-02 (427 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True Package: modem-manager-gui 0.0.16-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Tags: saucy Uname: Linux 3.11.0-26-generic x86_64 UpgradeStatus: Upgraded to saucy on 2014-08-01 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/modem-manager-gui/+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 1310338] Re: wifi stops working
Here is a way to temporary fix the problem: http://askubuntu.com/questions/442963/tl-wn821n-wifi-not-working- correctly/490992#490992 Maybe the fix in the github repo could be added into the next release? -- 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/1310338 Title: wifi stops working Status in “network-manager” package in Ubuntu: New Bug description: Hi! So I have TL-WN821N V4 USB wifi device. It connects to WIFI, I am able to download and upload stuff via terminal for as long as I want to. The problem occurs when I open up a browser (does not matter which one, have tried all). I open the browser and navigate to different pages. After like 5 minutes of browsing, I am not able to browse anymore. Wifi is still connected but no info is going though. I can also do a ping google.com in Terminal and it will yield no result. This bug occurs on my system that is running a fresh 14.04 Ubuntu 64 bit. It also occurred hwne I ran Ubuntu 13.10, and that is also the time I ran the wireless script shown below. Here is some info that I got with a script that is supposed to pur out a lot of info about my wifi: ## wireless info START ## # release # Distributor ID: Ubuntu Description:Ubuntu 13.10 Release:13.10 Codename: saucy # kernel # Linux kaspar-All-Series 3.11.0-19-generic #33-Ubuntu SMP Tue Mar 11 18:48:34 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux # lspci # 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c) Subsystem: ASUSTeK Computer Inc. Device [1043:8554] Kernel driver in use: r8169 # lsusb # Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter Bus 003 Device 003: ID 1532:000d Razer USA, Ltd Bus 003 Device 002: ID 046d:c326 Logitech, Inc. Bus 003 Device 005: ID 0781:5406 SanDisk Corp. Cruzer Micro U3 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # PCMCIA Card Info # # rfkill # # iw reg get # country 00: (2402 - 2472 @ 40), (6, 20) (2457 - 2482 @ 40), (6, 20), PASSIVE-SCAN, NO-IBSS (2474 - 2494 @ 20), (6, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS (5170 - 5250 @ 80), (6, 20), PASSIVE-SCAN, NO-IBSS (5735 - 5835 @ 80), (6, 20), PASSIVE-SCAN, NO-IBSS (57240 - 63720 @ 2160), (N/A, 0) # interfaces # # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback # iwconfig # # route # Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface # resolv.conf # # nm-tool # NetworkManager Tool State: disconnected - Device: eth0 - Type: Wired Driver:r8169 State: unavailable Default: no HW Address: Capabilities: Carrier Detect: yes Wired Properties Carrier: off # NetworkManager.state # [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true # NetworkManager.conf # [main] plugins=ifupdown,keyfile,ofono dns=dnsmasq [ifupdown] managed=false # iwlist # # iwlist channel # # lsmod # # modinfo # # modules # lp rtc # blacklist # [/etc/modprobe.d/blacklist-ath_pci.conf] blacklist ath_pci [/etc/modprobe.d/blacklist.conf] blacklist evbug blacklist usbmouse blacklist usbkbd blacklist eepro100 blacklist de4x5 blacklist eth1394 blacklist snd_intel8x0m blacklist snd_aw2 blacklist i2c_i801 blacklist prism54 blacklist bcm43xx blacklist garmin_gps blacklist asus_acpi blacklist snd_pcsp blacklist pcspkr blacklist amd76x_edac [/etc/modprobe.d/bumblebee.conf] blacklist nouveau blacklist nvidia blacklist nvidia-current blacklist nvidia-current-updates blacklist nvidia-304 blacklist nvidia-304-updates blacklist nvidia-experimental-304 blacklist nvidia-310 blacklist nvidia-310-updates blacklist nvidia-experimental-310 blacklist nvidia-313 blacklist nvidia-313-updates blacklist nvidia-experimental-313 blacklist nvidia-319 blacklist nvidia-319-updates blacklist nvidia-experimental-319 blacklist nvidia-325 blacklist nvidia-325-updates blacklist nvi
[Touch-packages] [Bug 1351950] [NEW] Ubuntu does not put CPU into idle state
Public bug reported: When booting into Windows partition, it manages to downclock and lower the V-core of my Intel i5-4570 CPU. This gives me a steady 25 C temperature during idle time. (measured with physical device and measured with Windows application called SpeedFan). On Ubuntu, this does not seem to happen. Even if I do echo "ondemand" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor , the CPU temperature is still about 40 C high during idle time. I do this measurement after clean boot, CPU usage is 0-6% and temp is 40 C steady. I use xsensors to look at my CPU temps and frequencies. This means that Ubuntu does not effectively downclock and lower the V-core of CPU when computer is in a idle state. I belive this is true to any version of Ubuntu now as I can see the effect on my Laptops that are using Ubuntu also. The battery life is much shorter than it is with Windows running on them. I have made my tests with a desktop computer using: CPU: i5-4570 GPU: GTX 760 Mobo: Asus B85-Plus OS: Ubuntu 14.04 64 bit Also made tests on various Lenovo thinkpads and Ultrabooks. Results remain the same, Ubuntu makes the CPU a lot hotter because of the reasons I posted. ** Affects: network-manager (Ubuntu) Importance: Undecided 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/1351950 Title: Ubuntu does not put CPU into idle state Status in “network-manager” package in Ubuntu: New Bug description: When booting into Windows partition, it manages to downclock and lower the V-core of my Intel i5-4570 CPU. This gives me a steady 25 C temperature during idle time. (measured with physical device and measured with Windows application called SpeedFan). On Ubuntu, this does not seem to happen. Even if I do echo "ondemand" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor , the CPU temperature is still about 40 C high during idle time. I do this measurement after clean boot, CPU usage is 0-6% and temp is 40 C steady. I use xsensors to look at my CPU temps and frequencies. This means that Ubuntu does not effectively downclock and lower the V-core of CPU when computer is in a idle state. I belive this is true to any version of Ubuntu now as I can see the effect on my Laptops that are using Ubuntu also. The battery life is much shorter than it is with Windows running on them. I have made my tests with a desktop computer using: CPU: i5-4570 GPU: GTX 760 Mobo: Asus B85-Plus OS: Ubuntu 14.04 64 bit Also made tests on various Lenovo thinkpads and Ultrabooks. Results remain the same, Ubuntu makes the CPU a lot hotter because of the reasons I posted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328305] Re: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails after a while
Forgot to answer, but that option "enable_msi=0" helped me, thanks! Now my /etc/modprobe.d/alsa-base.conf: options snd-usb-audio index=-2 options snd_hda_intel index=0 model=auto vid=1022 pid=780d probe_mask=1 enable_msi=0 options snd_hda_intel index=1 model=auto vid=1002 pid=9840 -- 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/1328305 Title: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails after a while Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: My sound stutters and skips in different web browser and on offline media players like rhythembox and vlc. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tat1842 F pulseaudio /dev/snd/controlC0: tat1842 F pulseaudio CurrentDesktop: GNOME Date: Mon Jun 9 23:56:42 2014 InstallationDate: Installed on 2014-05-22 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Sound works for a while, then breaks Title: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2163 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.22 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.11:bd07/19/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.22:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 08961030410620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1328305/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351916] Re: 4-pin jack mic doesn't work
I suggest trying latest kernel module/driver to make sure it has not been fixed already: https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS Once you have that done, reload ALSA (or just reboot) and run the following command to gather the logs: apport-collect 1351916 ** Package changed: pulseaudio (Ubuntu) => alsa-driver (Ubuntu) ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1351916 Title: 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1326954] Re: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: modemmanager (Ubuntu) Status: New => Confirmed -- 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/1326954 Title: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904) Status in “modemmanager” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwan0 (net)' - Numbers | own : 'unknown' -
[Touch-packages] [Bug 1351916] Re: 4-pin jack mic doesn't work
apport information ** Tags added: apport-collected trusty ** Description changed: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: nicolas3548 F pulseaudio + /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2014-07-16 (17 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + Package: alsa-driver (not installed) + ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 + Tags: trusty + Uname: Linux 3.13.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/21/2013 + dmi.bios.vendor: Phoenix Technologies Ltd. + dmi.bios.version: V2.18 + dmi.board.asset.tag: No Asset Tag + dmi.board.name: Aspire V5-571G + dmi.board.vendor: Acer + dmi.board.version: V2.18 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: Acer + dmi.chassis.version: V2.18 + dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: + dmi.product.name: Aspire V5-571G + dmi.product.version: V2.18 + dmi.sys.vendor: Acer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1351916/+attachment/4168755/+files/AlsaInfo.txt -- 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/1351916 Title: 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351916] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1351916/+attachment/4168756/+files/BootDmesg.txt -- 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/1351916 Title: 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351916] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1351916/+attachment/4168759/+files/PulseList.txt -- 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/1351916 Title: 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351916] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1351916/+attachment/4168758/+files/ProcEnviron.txt -- 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/1351916 Title: 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: cannot enter a long number with 22 digits
** Changed in: dialer-app (Ubuntu) Status: New => In Progress ** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) => Filip Sohajek (filip-sohajek) -- 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: In Progress 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 1351916] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1351916/+attachment/4168757/+files/CurrentDmesg.txt -- 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/1351916 Title: 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351916] Re: 4-pin jack mic doesn't work
My problems persists. -- 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/1351916 Title: 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1326954] Re: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904)
The logs indicate that the modem is perfectly indentified as a MBIM based modem using MBIM plugin, which works better than using the Sierra plugin, so that is expected. But when is the hang happening and how does the logs looks like at that time? ** Changed in: modemmanager (Ubuntu) Status: Confirmed => Incomplete ** Also affects: libmbim (Ubuntu) Importance: Undecided Status: New ** Changed in: libmbim (Ubuntu) Status: New => Incomplete ** Bug watch added: GNOME Bug Tracker #726613 https://bugzilla.gnome.org/show_bug.cgi?id=726613 ** Also affects: modemmanager via https://bugzilla.gnome.org/show_bug.cgi?id=726613 Importance: Unknown Status: Unknown -- 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/1326954 Title: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904) Status in ModemManager (with NetworkManager support): Unknown Status in “libmbim” package in Ubuntu: Confirmed Status in “modemmanager” package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98')
[Touch-packages] [Bug 1326954] Re: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904)
I'm sorry, it seems like it is in fact using the generic plugin instead of MBIM, probably after failing to use the latter. I think this issue is covered in the upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=726613 Private bug #1307932 might be a duplicate. ** Changed in: libmbim (Ubuntu) Status: Incomplete => Confirmed ** Changed in: modemmanager (Ubuntu) Status: Incomplete => Confirmed ** Changed in: modemmanager (Ubuntu) Status: Confirmed => 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/1326954 Title: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904) Status in ModemManager (with NetworkManager support): Unknown Status in “libmbim” package in Ubuntu: Confirmed Status in “modemmanager” package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte'
[Touch-packages] [Bug 1299441] Re: Regression: Qt Creator cannot run the executable
seem cmake- only bug ** Package changed: ubuntu-touch-meta (Ubuntu) => qtcreator-plugin-cmake -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1299441 Title: Regression: Qt Creator cannot run the executable Status in QtCreator CMakeProjectManager plugin: Confirmed Bug description: I cannot execute my application (CMake project) anymore in Qt Creator after compiling. It just says "No executable specified." even though I have selected the run target. This is regression as it has worked before. I'm using Qt Creator that came with ubuntu-sdk. So: 1) Import a (CMake) project 2) Compile 3) Select the run target 4) Click on the run button What should happen: - The selected binary should be lauched What happens instead: - "No executable specified." is outputted to the Application Output console. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-sdk (not installed) ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 29 14:17:54 2014 SourcePackage: ubuntu-touch-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qtcreator-plugin-cmake/+bug/1299441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349523] Re: Touchpad is not recognised on acer E5 771G
*** This bug is a duplicate of bug 1349522 *** https://bugs.launchpad.net/bugs/1349522 ** This bug has been marked a duplicate of bug 1349522 Touchpad is not recognised on acer E5 771G -- 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/1349523 Title: Touchpad is not recognised on acer E5 771G Status in “xorg” package in Ubuntu: New Bug description: HI all, my touchpad is not recognised on my new Acer Aspire E5-771G. The problems occurred right after the installation of Ubuntu. Strange enough sometimes it works and after the next boot it doesnt. On Windows 8.1 (i have dual boot) touchpad works fine. Touchpad is not recognised, this meas there is no entry in xinput - list and no entry in /proc/bus/input/devices. In these cases when touchpad is working there are entries. I tried gconftool statement, of course Fn+F7 every time, modprobe - r psmouse and so on. Nothing worked. Touchpad is by synaptics. Ubuntu version ist 14.04 Any help would be very appreciated. Thank you in advance ! Bernd Wollersheim 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 Date: Mon Jul 28 20:07:30 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0882] Subsystem: Acer Incorporated [ALI] Device [1025:0882] InstallationDate: Installed on 2014-07-19 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire E5-771G ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=5fe9f773-43c0-4098-aecd-8433aa1f2027 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/13/2014:svnAcer:pnAspireE5-771G:pvrTBDbyOEM:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-771G dmi.product.version: TBD by OEM dmi.sys.vendor: Acer 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: Mon Jul 28 19:57:47 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5941 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1349523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1326954] Re: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904)
** Changed in: modemmanager Status: Unknown => New ** Changed in: modemmanager Importance: Unknown => Medium -- 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/1326954 Title: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904) Status in ModemManager (with NetworkManager support): New Status in “libmbim” package in Ubuntu: Confirmed Status in “modemmanager” package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwan0 (n
[Touch-packages] [Bug 1351950] Re: Ubuntu does not put CPU into idle state
** Package changed: network-manager (Ubuntu) => powermanagement- interface (Ubuntu) -- 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/1351950 Title: Ubuntu does not put CPU into idle state Status in “powermanagement-interface” package in Ubuntu: New Bug description: When booting into Windows partition, it manages to downclock and lower the V-core of my Intel i5-4570 CPU. This gives me a steady 25 C temperature during idle time. (measured with physical device and measured with Windows application called SpeedFan). On Ubuntu, this does not seem to happen. Even if I do echo "ondemand" | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor , the CPU temperature is still about 40 C high during idle time. I do this measurement after clean boot, CPU usage is 0-6% and temp is 40 C steady. I use xsensors to look at my CPU temps and frequencies. This means that Ubuntu does not effectively downclock and lower the V-core of CPU when computer is in a idle state. I belive this is true to any version of Ubuntu now as I can see the effect on my Laptops that are using Ubuntu also. The battery life is much shorter than it is with Windows running on them. I have made my tests with a desktop computer using: CPU: i5-4570 GPU: GTX 760 Mobo: Asus B85-Plus OS: Ubuntu 14.04 64 bit Also made tests on various Lenovo thinkpads and Ultrabooks. Results remain the same, Ubuntu makes the CPU a lot hotter because of the reasons I posted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powermanagement-interface/+bug/1351950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332338] Re: New upstream release 0.9.8.10
A new version has been released. See new bug #1351977. -- 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/1332338 Title: New upstream release 0.9.8.10 Status in “network-manager” package in Ubuntu: Incomplete Bug description: Please package the new upstream stable release of network-manager. debdiff attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1332338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351977] [NEW] New upstream release 0.9.10.0
Public bug reported: Please update package in Utopic to 0.9.10.0. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Debian) Importance: Undecided Status: Fix Released ** Tags: upgrade-software-version ** Description changed: Please update package in Utopic to 0.9.10.0. - - ProblemType: Bug - DistroRelease: Ubuntu 14.04 - Package: network-manager 0.9.8.8-0ubuntu7 - ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 - Uname: Linux 3.13.0-32-generic x86_64 - NonfreeKernelModules: wl nvidia - ApportVersion: 2.14.1-0ubuntu3.2 - Architecture: amd64 - CurrentDesktop: Unity - Date: Sun Aug 3 21:01:36 2014 - DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-precise-amd64-20130203-1 - IfupdownConfig: - auto lo - iface lo inet loopback - InstallationDate: Installed on 2014-03-12 (144 days ago) - InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 - IpRoute: - default via 10.0.0.138 dev wlan1 proto static - 10.0.0.0/24 dev wlan1 proto kernel scope link src 10.0.0.105 metric 9 - NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true - RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no - SourcePackage: network-manager - UpgradeStatus: Upgraded to trusty on 2014-04-22 (103 days ago) - WifiSyslog: - - nmcli-dev: - DEVICE TYPE STATE DBUS-PATH - cdc-wdm0 gsm disconnected /org/freedesktop/NetworkManager/Devices/8 - wlan1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 - eth0 802-3-ethernetunavailable /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 -- 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/1351977 Title: New upstream release 0.9.10.0 Status in “network-manager” package in Ubuntu: New Status in “network-manager” package in Debian: Fix Released Bug description: Please update package in Utopic to 0.9.10.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351977] Re: New upstream release 0.9.10.0
** Also affects: network-manager (Debian) Importance: Undecided Status: New ** Changed in: network-manager (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1351977 Title: New upstream release 0.9.10.0 Status in “network-manager” package in Ubuntu: New Status in “network-manager” package in Debian: Fix Released Bug description: Please update package in Utopic to 0.9.10.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301015] Re: Networking does not restart
I'm also using:
# (ifdown eth0 ; ifup eth0) &
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1301015
Title:
Networking does not restart
Status in “ifupdown” package in Ubuntu:
Opinion
Bug description:
In Ubuntu Server 14.04 it appears it is not possible to restart
networking. This is fresh install from ISO.
wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
wirehive@ubuntu:~$ echo $?
1
wirehive@ubuntu:~$ sudo service networking restart
stop: Job failed while stopping
start: Job is already running: networking
wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
+ PATH=/sbin:/bin
+ RUN_DIR=/run/network
+ IFSTATE=/run/network/ifstate
+ STATEDIR=/run/network/state
+ '[' -x /sbin/ifup ']'
+ '[' -x /sbin/ifdown ']'
+ . /lib/lsb/init-functions
+++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
++ . /lib/lsb/init-functions.d/20-left-info-blocks
++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d
2>/dev/null)'
++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
++ . /lib/lsb/init-functions.d/50-ubuntu-logging
+++ LOG_DAEMON_MSG=
++ FANCYTTY=
++ '[' -e /etc/lsb-base-logging.sh ']'
++ true
+ CONFIGURE_INTERFACES=yes
+ EXCLUDE_INTERFACES=
+ VERBOSE=no
+ '[' -f /etc/default/networking ']'
+ verbose=
+ '[' no = yes ']'
+ case "$1" in
+ init_is_upstart
+ '[' -x /sbin/initctl ']'
+ /bin/grep -q upstart
+ /sbin/initctl version
+ return 0
+ exit 1
wirehive@ubuntu:~$ sudo bash -x service networking restart
++ basename service
+ VERSION='service ver. 0.91-ubuntu1'
++ basename service
+ USAGE='Usage: service < option > | --status-all | [ service_name [ command
| --full-restart ] ]'
+ SERVICE=
+ ACTION=
+ SERVICEDIR=/etc/init.d
+ OPTIONS=
+ '[' 2 -eq 0 ']'
+ cd /
+ '[' 2 -gt 0 ']'
+ case "${1}" in
+ '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
+ '[' 2 -eq 2 -a restart = --full-restart ']'
+ '[' -z '' ']'
+ SERVICE=networking
+ shift
+ '[' 1 -gt 0 ']'
+ case "${1}" in
+ '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
+ '[' 1 -eq 2 -a '' = --full-restart ']'
+ '[' -z networking ']'
+ '[' -z '' ']'
+ ACTION=restart
+ shift
+ '[' 0 -gt 0 ']'
+ '[' -r /etc/init/networking.conf ']'
+ which initctl
+ grep -q upstart
+ initctl version
+ case "${ACTION}" in
+ stop networking
stop: Job failed while stopping
+ :
+ exec start networking
start: Job is already running: networking
wirehive@ubuntu:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332338] Re: New upstream release 0.9.8.10
Any progress here? Seems like the packages in the branch builds fine for me, even for Trusty. -- 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/1332338 Title: New upstream release 0.9.8.10 Status in “network-manager” package in Ubuntu: Incomplete Bug description: Please package the new upstream stable release of network-manager. debdiff attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1332338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 663785] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/663785/+attachment/4168856/+files/ProcEnviron.txt -- 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/663785 Title: kubuntu powerdevil does not allow scaling in 10.10 Status in “pm-utils” package in Ubuntu: Incomplete Bug description: Up to 10.04 I could set cpu scaling policy in my powerdevil profiles. In 10.10, it's gone. Not good! My cpu runs at 2.00GHz all the time and is close to overheating! --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (107 days ago) UserGroups: adm cdrom davfs2 dip fuse kismet lp lpadmin plugdev pulse-access sambashare scanner sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/663785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 663785] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/663785/+attachment/4168855/+files/Dependencies.txt -- 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/663785 Title: kubuntu powerdevil does not allow scaling in 10.10 Status in “pm-utils” package in Ubuntu: Incomplete Bug description: Up to 10.04 I could set cpu scaling policy in my powerdevil profiles. In 10.10, it's gone. Not good! My cpu runs at 2.00GHz all the time and is close to overheating! --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (107 days ago) UserGroups: adm cdrom davfs2 dip fuse kismet lp lpadmin plugdev pulse-access sambashare scanner sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/663785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 663785] Re: kubuntu powerdevil does not allow scaling in 10.10
Well, I still cannot set cpu scaling in powerdevil, but the cpu does not run at the highest speed any more. So it's kind of halfway fixed... ;-) (Kubuntu 14.04 64bit) ** Tags added: apport-collected trusty ** Description changed: - Up to 10.04 I could set cpu scaling policy in my powerdevil profiles. In - 10.10, it's gone. Not good! My cpu runs at 2.00GHz all the time and is - close to overheating! + Up to 10.04 I could set cpu scaling policy in my powerdevil profiles. In 10.10, it's gone. Not good! My cpu runs at 2.00GHz all the time and is close to overheating! + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 14.04 + Package: pm-utils 1.4.1-13ubuntu0.1 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 + Tags: trusty + Uname: Linux 3.13.0-32-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2014-04-18 (107 days ago) + UserGroups: adm cdrom davfs2 dip fuse kismet lp lpadmin plugdev pulse-access sambashare scanner sudo vboxusers + _MarkForUpload: True -- 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/663785 Title: kubuntu powerdevil does not allow scaling in 10.10 Status in “pm-utils” package in Ubuntu: Incomplete Bug description: Up to 10.04 I could set cpu scaling policy in my powerdevil profiles. In 10.10, it's gone. Not good! My cpu runs at 2.00GHz all the time and is close to overheating! --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.1 PackageArchitecture: all ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-18 (107 days ago) UserGroups: adm cdrom davfs2 dip fuse kismet lp lpadmin plugdev pulse-access sambashare scanner sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/663785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351982] [NEW] top panel and launcher are unresponsive
Public bug reported: Unity has recently (~2014-07-15) started exhibiting two odd behaviors that are likely related: 1) The launcher, which is set to autohide, will appear and disappear in <1s (even though I hover over the launcher). It is unresponsive to clicks. 2) All applets in the top panel are unresponsive to clicks. 1 & 2 always occur together at some point during a session. That is, these components work correctly for hours (days?), then become unresponsive. I have not yet identified the trigger event; screenlocking or suspend/resume *may* be related, but not reliably so (i.e., I can't reproduce it this way). Restarting unity-panel-service (killall unity-panel-service) doesn't help. The problem is temporarily fixed by logging out/in or rebooting, but the issue recurs. The timing of the first occurrence (in July) is probably consistent with my first use of unity-tweak-tool to set focus follows mouse, although this hypothesis doesn't explain why the components initially work and then become unresponsive. Otherwise, my config is pretty stock. 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 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,mousepoll,snap,resize,move,grid,unitymtgrabhandles,place,regex,gnomecompat,vpswitch,animation,expo,workarounds,ezoom,wall,session,fade,scale,unityshell] CurrentDesktop: Unity Date: Sun Aug 3 12:17:34 2014 InstallationDate: Installed on 2012-10-09 (662 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-21 (103 days ago) ** Affects: unity (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 unity in Ubuntu. https://bugs.launchpad.net/bugs/1351982 Title: top panel and launcher are unresponsive Status in “unity” package in Ubuntu: New Bug description: Unity has recently (~2014-07-15) started exhibiting two odd behaviors that are likely related: 1) The launcher, which is set to autohide, will appear and disappear in <1s (even though I hover over the launcher). It is unresponsive to clicks. 2) All applets in the top panel are unresponsive to clicks. 1 & 2 always occur together at some point during a session. That is, these components work correctly for hours (days?), then become unresponsive. I have not yet identified the trigger event; screenlocking or suspend/resume *may* be related, but not reliably so (i.e., I can't reproduce it this way). Restarting unity-panel-service (killall unity-panel-service) doesn't help. The problem is temporarily fixed by logging out/in or rebooting, but the issue recurs. The timing of the first occurrence (in July) is probably consistent with my first use of unity-tweak-tool to set focus follows mouse, although this hypothesis doesn't explain why the components initially work and then become unresponsive. Otherwise, my config is pretty stock. 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 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,mousepoll,snap,resize,move,grid,unitymtgrabhandles,place,regex,gnomecompat,vpswitch,animation,expo,workarounds,ezoom,wall,session,fade,scale,unityshell] CurrentDesktop: Unity Date: Sun Aug 3 12:17:34 2014 InstallationDate: Installed on 2012-10-09 (662 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-21 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 957231] Re: update-manager crashed with SIGSEGV in debListParser::LoadReleaseInfo()
Any update on the SRU for Precise? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/957231 Title: update-manager crashed with SIGSEGV in debListParser::LoadReleaseInfo() Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Precise: Triaged Status in “apt” source package in Saucy: Triaged Status in “apt” source package in Trusty: Fix Released Status in “update-manager” source package in Trusty: Invalid Bug description: just would not complete the update ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.8 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Fri Mar 16 17:46:18 2012 ExecutablePath: /usr/bin/update-manager GsettingsChanges: com.ubuntu.update-manager first-run false com.ubuntu.update-manager launch-time 1331920010 com.ubuntu.update-manager show-details true com.ubuntu.update-manager window-height 932 com.ubuntu.update-manager window-width 731 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/update-manager ProcEnviron: SHELL=/bin/bash LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f4c9838a019 <_ZN13debListParser15LoadReleaseInfoERN8pkgCache15PkgFileIteratorER6FileFdSs+1561>: mov%eax,0x14(%rbx) PC (0x7f4c9838a019) ok source "%eax" ok destination "0x14(%rbx)" (0x7f4c7bfea5c4) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: update-manager StacktraceTop: debListParser::LoadReleaseInfo(pkgCache::PkgFileIterator&, FileFd&, std::string) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 debPackagesIndex::Merge(pkgCacheGenerator&, OpProgress*) const () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 ?? () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 pkgCacheGenerator::MakeStatusCache(pkgSourceList&, OpProgress*, MMap**, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 pkgCacheFile::BuildCaches(OpProgress*, bool) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 Title: update-manager crashed with SIGSEGV in debListParser::LoadReleaseInfo() UpgradeStatus: Upgraded to precise on 2012-03-07 (8 days ago) UserGroups: adm audio avahi avahi-autoipd backup bin bluetooth cdrom clamav colord couchdb crontab daemon dialout dip disk fax floppy fuse games gdm gnats kmem libuuid lightdm list lp lpadmin mail man messagebus mlocate netdev news ntp operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl scanner shadow src ssh ssl-cert staff sudo sys syslog tape tty users utempter utmp uucp vboxusers video voice whoopsie www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/957231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351982] Re: top panel and launcher are unresponsive
Also: Drag and drop no longer work. For example, dragging a file from nautilus to gnome-terminal no longer inserts the file path. -- 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/1351982 Title: top panel and launcher are unresponsive Status in “unity” package in Ubuntu: New Bug description: Unity has recently (~2014-07-15) started exhibiting two odd behaviors that are likely related: 1) The launcher, which is set to autohide, will appear and disappear in <1s (even though I hover over the launcher). It is unresponsive to clicks. 2) All applets in the top panel are unresponsive to clicks. 1 & 2 always occur together at some point during a session. That is, these components work correctly for hours (days?), then become unresponsive. I have not yet identified the trigger event; screenlocking or suspend/resume *may* be related, but not reliably so (i.e., I can't reproduce it this way). Restarting unity-panel-service (killall unity-panel-service) doesn't help. The problem is temporarily fixed by logging out/in or rebooting, but the issue recurs. The timing of the first occurrence (in July) is probably consistent with my first use of unity-tweak-tool to set focus follows mouse, although this hypothesis doesn't explain why the components initially work and then become unresponsive. Otherwise, my config is pretty stock. 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 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,mousepoll,snap,resize,move,grid,unitymtgrabhandles,place,regex,gnomecompat,vpswitch,animation,expo,workarounds,ezoom,wall,session,fade,scale,unityshell] CurrentDesktop: Unity Date: Sun Aug 3 12:17:34 2014 InstallationDate: Installed on 2012-10-09 (662 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-21 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351982/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343341] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::
The stack trace on this bug has improved, please look again at the errors.u.c link This is currently the most common crash on the phone -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1343341 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::dbus::Bus::send_with_reply_and_block_for_at_most Status in “indicator-network” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20140715-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/eb8fe775c22d5210f56ad7ac038ac1b1895f4465 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1343341/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Here the launcher icon 'tooltip' will always remain until - The cursor touches another launcher icon The cursor touches anything selectable, examples are - Unity panel Nautilus sidebar Any file on Desktop or in file browser window Anything selectable in an Internet browser The field or toolbar of a text editor like gedit Clicking on the Desktop ect. -- 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
The other time they always disappear is if there is any open window that has any sort of activity going on, like a terminal running, a player playing, an animation or vid in an internet browser, ... -- 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 1351989] [NEW] compiz crashed with signal 5 in _XReply()
Public bug reported: I downloaded this https://www.dropbox.com/sh/b8q1rcon5srs3l7/AACiok8UO4aB6jCxTifcaeA7a/Siluro.zip Watch some photo, used rotation, then close without save. Next, PC freeze for a few seconds, compiz crash. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 3 22:58:42 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-05 (120 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) ProcCmdline: compiz Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: unity (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash utopic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1351989 Title: compiz crashed with signal 5 in _XReply() Status in “unity” package in Ubuntu: New Bug description: I downloaded this https://www.dropbox.com/sh/b8q1rcon5srs3l7/AACiok8UO4aB6jCxTifcaeA7a/Siluro.zip Watch some photo, used rotation, then close without save. Next, PC freeze for a few seconds, compiz crash. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 3 22:58:42 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-05 (120 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) ProcCmdline: compiz Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351989]
StacktraceTop: XGetWindowProperty (dpy=0x1f1b9b0, w=65011719, property=property@entry=67, offset=offset@entry=0, length=length@entry=8192, delete=delete@entry=0, req_type=req_type@entry=31, actual_type=actual_type@entry=0x7fff225f4db0, actual_format=actual_format@entry=0x7fff225f4dac, nitems=nitems@entry=0x7fff225f4db8, bytesafter=bytesafter@entry=0x7fff225f4dc0, prop=prop@entry=0x7fff225f4dc8) at ../../src/GetProp.c:69 XGetClassHint (dpy=, w=, classhint=0x7fff225f5060) at ../../src/GetHints.c:311 ?? () from /tmp/apport_sandbox_KuOrF1/usr/lib/compiz/libunityshell.so unity::decoration::ForceQuitDialog::ForceQuitDialog(CompWindow*, unsigned long) () from /tmp/apport_sandbox_KuOrF1/usr/lib/compiz/libunityshell.so unity::decoration::Window::Impl::ShowForceQuitDialog(bool, unsigned long) () from /tmp/apport_sandbox_KuOrF1/usr/lib/compiz/libunityshell.so -- 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/1351989 Title: compiz crashed with signal 5 in _XReply() Status in “unity” package in Ubuntu: New Bug description: I downloaded this https://www.dropbox.com/sh/b8q1rcon5srs3l7/AACiok8UO4aB6jCxTifcaeA7a/Siluro.zip Watch some photo, used rotation, then close without save. Next, PC freeze for a few seconds, compiz crash. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 3 22:58:42 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-05 (120 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) ProcCmdline: compiz Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351989] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1351989/+attachment/4168874/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1351989 Title: compiz crashed with signal 5 in _XReply() Status in “unity” package in Ubuntu: New Bug description: I downloaded this https://www.dropbox.com/sh/b8q1rcon5srs3l7/AACiok8UO4aB6jCxTifcaeA7a/Siluro.zip Watch some photo, used rotation, then close without save. Next, PC freeze for a few seconds, compiz crash. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 3 22:58:42 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-05 (120 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) ProcCmdline: compiz Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351989] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1351989/+attachment/4168873/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1351989 Title: compiz crashed with signal 5 in _XReply() Status in “unity” package in Ubuntu: New Bug description: I downloaded this https://www.dropbox.com/sh/b8q1rcon5srs3l7/AACiok8UO4aB6jCxTifcaeA7a/Siluro.zip Watch some photo, used rotation, then close without save. Next, PC freeze for a few seconds, compiz crash. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 3 22:58:42 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-05 (120 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) ProcCmdline: compiz Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351989] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1351989/+attachment/4168875/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1351989/+attachment/4168864/+files/CoreDump.gz ** Changed in: unity (Ubuntu) Importance: Undecided => Medium ** Tags removed: need-amd64-retrace -- 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/1351989 Title: compiz crashed with signal 5 in _XReply() Status in “unity” package in Ubuntu: New Bug description: I downloaded this https://www.dropbox.com/sh/b8q1rcon5srs3l7/AACiok8UO4aB6jCxTifcaeA7a/Siluro.zip Watch some photo, used rotation, then close without save. Next, PC freeze for a few seconds, compiz crash. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Aug 3 22:58:42 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-05 (120 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) ProcCmdline: compiz Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetClassHint () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1351989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330037] Re: upower 0.99 transition
So the device management issues in kde were unrelated to upower 0.99, which leaves the suspend issues with upstart where I'm working on a fix. ** Package changed: kde4libs (Ubuntu) => kde-workspace (Ubuntu) ** Changed in: kde-workspace (Ubuntu) Status: New => In Progress -- 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/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: Invalid Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: In Progress Status in “gnome-session” package in Ubuntu: In Progress Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “gnome-shell” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: Triaged Status in “kde-workspace” package in Ubuntu: In Progress Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: In Progress Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: In Progress Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: In Progress Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery and sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351916] Re: 4-pin jack mic doesn't work
** Changed in: alsa-driver (Ubuntu) Status: Incomplete => New ** Summary changed: - 4-pin jack mic doesn't work + [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352000] [NEW] Screen repeatedly goes black, returns to normal after a couple of seconds
Public bug reported: Running 14.04. My screen (an external monitor, connected to a desktop computer) has started going black and then returning back to normal a couple of seconds later. This happens every few minutes. dmesg shows lines: [ 9241.255109] HDMI: ELD buf size is 0, force 128 [ 9241.255132] HDMI: invalid ELD data byte 0 There does not seem to be anything relevant being added to Xorg.0.log. 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: Sun Aug 3 22:00:36 2014 DistUpgraded: 2014-04-25 18:09:11,162 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8534] InstallationDate: Installed on 2014-04-07 (118 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=ad1b3110-ee9a-4dac-839d-604080e0020d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-25 (100 days ago) dmi.bios.date: 12/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: PCS dmi.chassis.type: 3 dmi.chassis.vendor: PC SPECIALIST dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1707:bd12/13/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-A:rvrRev1.xx:cvnPCSPECIALIST:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS 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: Sun Aug 3 19:24:59 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10147 vendor ACI xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1352000 Title: Screen repeatedly goes black, returns to normal after a couple of seconds Status in “xorg” package in Ubuntu: New Bug description: Running 14.04. My screen (an external monitor, connected to a desktop computer) has started going black and then returning back to normal a couple of seconds later. This happens every few minutes. dmesg shows lines: [ 9241.255109] HDMI: ELD buf size is 0, force 128 [ 9241.255132] HDMI: invalid ELD data byte 0 There does not seem to be anything relevant being added to Xorg.0.log. 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: Sun Aug 3 22:00:36 2014 DistUpgraded: 2014-04-25 18:09:11,162 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
[Touch-packages] [Bug 1352012] Re: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1352012 Title: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected Status in “base-files” package in Ubuntu: New Bug description: Not sure what else happened. I just got a dialog box about this failing. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: base-files 7.2ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 Date: Sun Aug 3 16:22:49 2014 Dependencies: DpkgTerminalLog: Preparing to unpack .../base-files_7.2ubuntu5.1_i386.deb ... Unpacking base-files (7.2ubuntu5.1) over (7.2ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/base-files_7.2ubuntu5.1_i386.deb (--unpack): unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected DuplicateSignature: package:base-files:7.2ubuntu5:unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected ErrorMessage: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected InstallationDate: Installed on 2013-05-16 (444 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) SourcePackage: base-files Title: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected UpgradeStatus: Upgraded to trusty on 2014-05-03 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1352012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352012] [NEW] package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected
Public bug reported: Not sure what else happened. I just got a dialog box about this failing. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: base-files 7.2ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 Date: Sun Aug 3 16:22:49 2014 Dependencies: DpkgTerminalLog: Preparing to unpack .../base-files_7.2ubuntu5.1_i386.deb ... Unpacking base-files (7.2ubuntu5.1) over (7.2ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/base-files_7.2ubuntu5.1_i386.deb (--unpack): unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected DuplicateSignature: package:base-files:7.2ubuntu5:unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected ErrorMessage: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected InstallationDate: Installed on 2013-05-16 (444 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) SourcePackage: base-files Title: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected UpgradeStatus: Upgraded to trusty on 2014-05-03 (92 days ago) ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1352012 Title: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected Status in “base-files” package in Ubuntu: New Bug description: Not sure what else happened. I just got a dialog box about this failing. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: base-files 7.2ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 Date: Sun Aug 3 16:22:49 2014 Dependencies: DpkgTerminalLog: Preparing to unpack .../base-files_7.2ubuntu5.1_i386.deb ... Unpacking base-files (7.2ubuntu5.1) over (7.2ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/base-files_7.2ubuntu5.1_i386.deb (--unpack): unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected DuplicateSignature: package:base-files:7.2ubuntu5:unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected ErrorMessage: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected InstallationDate: Installed on 2013-05-16 (444 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) SourcePackage: base-files Title: package base-files 7.2ubuntu5 failed to install/upgrade: unable to stat `./mnt' (which I was about to install): Transport endpoint is not connected UpgradeStatus: Upgraded to trusty on 2014-05-03 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1352012/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330770] Re: click packages rely upon tls for integrity and authenticity
** Changed in: click-package-index Assignee: James Tait (jamestait) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1330770 Title: click packages rely upon tls for integrity and authenticity Status in Click Package metadata search service: Fix Committed Status in Online service used by software center: New Status in Click Packages Scope for Unity: New Status in “click” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-scope-click” package in Ubuntu: New Bug description: Hello, I just completed a quick review of the click source and the unity-scope-click source and behaviours, and found some opportunities for improvement. Debian, and Ubuntu, rely upon signed repository files with cryptographic hashes of packages to provide both integrity and authenticity checks for the packages hosted on that repository. The click framework and the unity-scope-click discovery and installation tool do not use signed repository files, nor do they have signatures of any sort on downloaded packages. The only integrity and authenticity checks are provided by the use of HTTPS. The click verify command will check files within the archive against MD5sums stored inside the archive but the click verify command is not used during package installation. (This is suitable for validating integrity against accidental changes only.) While it appears that unity-scope-click properly uses HTTPS to download package metadata and packages, HTTPS alone is insufficient for our needs: - Someone in a position to create new certificates at any of several hundred certificate authorities could create certificates purporting to be our update servers. This actual problem has been discovered in the wild with several certificate authorities issuing wild-card certificates or even certificates with signing authority. - X.509 is extremely complicated; TLS is extremely complicated. Flaws in both are inevitable. - HTTPS prevents the use of caching. - HTTPS only 'works' for data-in-motion; it is useless for data-at- rest integrity and authenticity checks. I have not yet reviewed the tools that application authors will use to upload their packages to our distribution servers but note in passing that most of these issues are also issues for adding packages to our update servers -- packages in flight within our network can be corrupted for many reasons, packages on disk can be corrupted for many reasons. A signature mechanism can protect against internal network faults, storage faults, and provide assurance months or years later that an uploaded package was uploaded by someone in control of a corresponding private key. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/click-package-index/+bug/1330770/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
As a workaround If you click on one of the indicators and click back on the password field you can type your password right away. -- 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: Confirmed 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 1351610] Re: LightDM looses focus
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/1351610 Title: LightDM looses focus Status in “unity” package in Ubuntu: Confirmed 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 1350803] Re: [Spread] Threashold in spread for closing apps should be increased
** Changed in: unity8 Status: New => Incomplete ** Changed in: unity8 Assignee: (unassigned) => Michael Zanetti (mzanetti) ** Changed in: ubuntu-ux Status: Fix Committed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1350803 Title: [Spread] Threashold in spread for closing apps should be increased Status in Ubuntu UX bugs: New Status in The Unity 8 shell: Incomplete Status in “unity8” package in Ubuntu: New Bug description: Currently, the close threshold is too small (you can close app with a fast swipe even for short distance movement), should be increased To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317476] Re: read builtin does not timeout when using readline for input
** Branch linked: lp:debian/bash -- 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/1317476 Title: read builtin does not timeout when using readline for input Status in “bash” package in Ubuntu: New Bug description: As of 14.04 the read builtin seemingly ignores -t if -e is provided. In 13.10, $ time read -t2 -e -p "? " ? real 0m2.000s user 0m0.000s sys 0m0.000s In 14.04, $ time read -t2 -e -p "? " ? ^C real 0m5.254s user 0m0.000s sys 0m0.000s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1317476/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug could also expose your password to someone looking over your shoulder when you unlock your 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/1351610 Title: LightDM looses focus Status in “unity” package in Ubuntu: Confirmed 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 1252733] Re: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume
It looks like i have the 1028:05fe version. My alsa-info is at http://www.alsa-project.org/db/?f=d5bad039a29e3d40892f395d64d43c8c31e4ecf1 Unfortunately downloading the newest daily driver didn't work, as the white noise is still there. -- 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/1252733 Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: When listening to sound on my laptop through headphones, there's a constant background hiss (which disappears only when all sound has been stopped for a few seconds. power saving I guess). I also need to turn the volume *way* down to 10% for the sound volume to be reasonable (it's way too loud otherwise). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: martijn2130 F pulseaudio /dev/snd/pcmC1D0p: martijn2130 F...m pulseaudio /dev/snd/controlC0: martijn2130 F pulseaudio Date: Tue Nov 19 14:26:46 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-13 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Intern geluid - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/24/2013:svnDellInc.:pnXPS12-9Q33:pvrA03:rvnDellInc.:rnXPS12-9Q33:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1252733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351951] Re: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()
** Description changed: - Bug in version 1.0.2, duplicaded of Bug #1342923 + Bug in version 1.0.2, duplicaded of Bug #1342923(?) ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: tracker 1.0.2-1ubuntu2 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 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Aug 3 12:43:09 2014 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2014-04-27 (98 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: - Segfault happened at: 0x7f23da50ee13 <_IO_vfprintf_internal+7443>: repnz scas %es:(%rdi),%al - PC (0x7f23da50ee13) ok - source "%es:(%rdi)" (0xc0449a50) not located in a known VMA region (needed readable region)! - destination "%al" ok - Stack memory exhausted (SP below stack segment) + Segfault happened at: 0x7f23da50ee13 <_IO_vfprintf_internal+7443>: repnz scas %es:(%rdi),%al + PC (0x7f23da50ee13) ok + source "%es:(%rdi)" (0xc0449a50) 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=0x7f23d619b640, format=, format@entry=0x7f23db83dae0 "Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s')", ap=ap@entry=0x7f23d619b7e8) at vfprintf.c:1642 - __GI___vasprintf_chk (result_ptr=0x7f23d619b798, flags=1, format=0x7f23db83dae0 "Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s')", args=0x7f23d619b7e8) 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 + _IO_vfprintf_internal (s=s@entry=0x7f23d619b640, format=, format@entry=0x7f23db83dae0 "Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s')", ap=ap@entry=0x7f23d619b7e8) at vfprintf.c:1642 + __GI___vasprintf_chk (result_ptr=0x7f23d619b798, flags=1, format=0x7f23db83dae0 "Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s')", args=0x7f23d619b7e8) 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 kvm libvirtd lpadmin plugdev sambashare sudo ** Bug watch added: GNOME Bug Tracker #734211 https://bugzilla.gnome.org/show_bug.cgi?id=734211 ** Also affects: tracker via https://bugzilla.gnome.org/show_bug.cgi?id=734211 Importance: Unknown Status: Unknown ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1351951 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() Status in Meta-tracker: Unknown Status in “tracker” package in Ubuntu: New Bug description: Bug in version 1.0.2, duplicaded of Bug #1342923(?) ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: tracker 1.0.2-1ubuntu2 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 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Aug 3 12:43:09 2014 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2014-04-27 (98 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x7f23da50ee13 <_IO_vfprintf_internal+7443>: repnz scas %es:(%rdi),%al PC (0x7f23da50ee13) ok source "%es:(%rdi)" (0xc0449a50) 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=0x7f23d619b640, format=, format@entry=0x7f23db83dae0 "Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s')", ap=ap@entry=0x7f23d619b7e8) at vfprintf.c:1642 __GI___vasprintf_chk (result_ptr=0x7f23d619b798, flags=1,
[Touch-packages] [Bug 1351815] Re: StartTransientUnit signature has changed in systemd 214
Yes it can wait until 214 is ready to land, not sure its worth supporting both API's -- 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: Triaged 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 1252733] Re: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume
control.10 {
iface MIXER
name 'Capture Source'
value 'Internal Mic'
comment {
access 'read write'
type ENUMERATED
count 1
item.0 'Headphone Mic'
item.1 'Headset Mic'
item.2 'Internal Mic'
}
}
control.17 {
iface CARD
name 'Headphone Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
control.18 {
iface CARD
name 'Headset Mic Phantom Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
Headset Mic Phantom Jack - indicates headset jack where hardware can not
distinguish between headphones and headsets
do capture mean hardware cannot distinguish bewteen headset Mic ,Mic or
headphone ?
if driver set it to headphone mode by default
how do the user switch between headphone, headset , mic mode without
using pa_backend.c for those who don't use pulseaudio ?
--
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/1252733
Title:
[XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background
noise or low volume
Status in “alsa-driver” package in Ubuntu:
Incomplete
Bug description:
When listening to sound on my laptop through headphones, there's a
constant background hiss (which disappears only when all sound has
been stopped for a few seconds. power saving I guess).
I also need to turn the volume *way* down to 10% for the sound volume
to be reasonable (it's way too loud otherwise).
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: martijn2130 F pulseaudio
/dev/snd/pcmC1D0p: martijn2130 F...m pulseaudio
/dev/snd/controlC0: martijn2130 F pulseaudio
Date: Tue Nov 19 14:26:46 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-13 (6 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Intern geluid - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: High background noise, or volume is too low
Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background
noise or low volume
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: XPS 12-9Q33
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA03:bd09/24/2013:svnDellInc.:pnXPS12-9Q33:pvrA03:rvnDellInc.:rnXPS12-9Q33:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 12-9Q33
dmi.product.version: A03
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1252733/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351951] Re: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal()
** Changed in: tracker Status: Unknown => New ** Changed in: tracker Importance: Unknown => Critical -- 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/1351951 Title: tracker-store crashed with SIGSEGV in _IO_vfprintf_internal() Status in Meta-tracker: New Status in “tracker” package in Ubuntu: New Bug description: Bug in version 1.0.2, duplicaded of Bug #1342923(?) ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: tracker 1.0.2-1ubuntu2 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 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Aug 3 12:43:09 2014 ExecutablePath: /usr/lib/tracker/tracker-store InstallationDate: Installed on 2014-04-27 (98 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x7f23da50ee13 <_IO_vfprintf_internal+7443>: repnz scas %es:(%rdi),%al PC (0x7f23da50ee13) ok source "%es:(%rdi)" (0xc0449a50) 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=0x7f23d619b640, format=, format@entry=0x7f23db83dae0 "Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s')", ap=ap@entry=0x7f23d619b7e8) at vfprintf.c:1642 __GI___vasprintf_chk (result_ptr=0x7f23d619b798, flags=1, format=0x7f23db83dae0 "Unable to insert multiple values for subject `%s' and single valued property `%s' (old_value: '%s', new value: '%s')", args=0x7f23d619b7e8) 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 kvm libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/1351951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1252733] Re: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume
if the user manual mention that it support headset, headphone and Mic, removing 0x19 is just a dirty workaround since HP Jack support OUT and not support IN seem really use 0x19 for Mic jack Node 0x15 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out Control: name="Headphone Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Control: name="Headphone Jack", index=0, device=0 Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-Out vals: [0x00 0x00] Pincap 0x0001001c: OUT HP EAPD Detect EAPD 0x2: EAPD Pin Default 0x0321101f: [Jack] HP Out at Ext Left Conn = 1/8, Color = Black DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0xc0: OUT HP Unsolicited: tag=01, enabled=1 Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Connection: 3 0x0c* 0x0d 0x0e -- 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/1252733 Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: When listening to sound on my laptop through headphones, there's a constant background hiss (which disappears only when all sound has been stopped for a few seconds. power saving I guess). I also need to turn the volume *way* down to 10% for the sound volume to be reasonable (it's way too loud otherwise). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: martijn2130 F pulseaudio /dev/snd/pcmC1D0p: martijn2130 F...m pulseaudio /dev/snd/controlC0: martijn2130 F pulseaudio Date: Tue Nov 19 14:26:46 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-13 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Intern geluid - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 12-9Q33, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/24/2013:svnDellInc.:pnXPS12-9Q33:pvrA03:rvnDellInc.:rnXPS12-9Q33:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1252733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
9.684335] sound hdaudioC0D0: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [9.684341] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [9.684344] sound hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [9.684346] sound hdaudioC0D0:mono: mono_out=0x0 [9.684348] sound hdaudioC0D0:inputs: [9.684351] sound hdaudioC0D0: Mic=0x1b seem missing headset mic the realtek codec need vendor specific coeff to support headset Mic , you have to ask the Acer support forum -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295837] Re: keyboard doesnt work after hibernation lockscreen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1295837 Title: keyboard doesnt work after hibernation lockscreen Status in “lightdm” package in Ubuntu: Confirmed Bug description: when i open the lid to my laptop the keybaord doesnt work in the lockscreen unless i go up to the power cog and go to switch account then i can log back in just fine it only happens when my laptop lid has been shut for more then 5 mins... This is for ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1295837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295837] Re: keyboard doesnt work after hibernation lockscreen
Probably seeing the same here on an Thinkpad X230 with Ubuntu 14.04. Didn't have this issue until recently. The keyboard input doesn't work until I interact with the icons in the top-bar. Just clicking and dismissing the cog menu is enough to make keyboard input work again. -- 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/1295837 Title: keyboard doesnt work after hibernation lockscreen Status in “lightdm” package in Ubuntu: Confirmed Bug description: when i open the lid to my laptop the keybaord doesnt work in the lockscreen unless i go up to the power cog and go to switch account then i can log back in just fine it only happens when my laptop lid has been shut for more then 5 mins... This is for ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1295837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351903] Re: network-manager-gnome 0.9.8.8-0ubuntu4.3 & or associated libraries cause HUGE memory usage on wlan0
** Description changed: Network-manager-gnome 0.9.8.8-0ubuntu4.3 & associated libraries cause HUGE memory usage on wlan0. Usage of wlan0 by any net app causes resident memory consumption by NMG to grow until all system memory is used and system becomes unresponsive. Reverting to previous version of NMG (0.9.8.8-0ubuntu4.2) eliminates the issue and fucntions as expected. Xubuntu 14.04 LTS up-to-date AMD64 - Toshiba CD560 Laptop + Toshiba C650D Laptop w/ Qualcomm Atheros AR8152 v1.1 Fast Ethernet adaptor -- 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/1351903 Title: network-manager-gnome 0.9.8.8-0ubuntu4.3 & or associated libraries cause HUGE memory usage on wlan0 Status in “network-manager” package in Ubuntu: New Bug description: Network-manager-gnome 0.9.8.8-0ubuntu4.3 & associated libraries cause HUGE memory usage on wlan0. Usage of wlan0 by any net app causes resident memory consumption by NMG to grow until all system memory is used and system becomes unresponsive. This takes several hours, but is consistent and unavoidable. Reverting to previous version of NMG (0.9.8.8-0ubuntu4.2) eliminates the issue and NMG functions as expected. Xubuntu 14.04 LTS up-to-date AMD64 Toshiba C650D Laptop w/ Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351903] Re: network-manager-gnome 0.9.8.8-0ubuntu4.3 & or associated libraries cause HUGE memory usage on wlan0
** Description changed: Network-manager-gnome 0.9.8.8-0ubuntu4.3 & associated libraries cause HUGE memory usage on wlan0. Usage of wlan0 by any net app causes resident memory consumption by NMG to grow until all system memory is used and system becomes unresponsive. Reverting to previous version of NMG (0.9.8.8-0ubuntu4.2) eliminates the - issue and fucntions as expected. + issue and NMG functions as expected. Xubuntu 14.04 LTS up-to-date AMD64 - Toshiba C650D Laptop w/ Qualcomm Atheros AR8152 v1.1 Fast Ethernet adaptor + Toshiba C650D Laptop w/ Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter ** Description changed: Network-manager-gnome 0.9.8.8-0ubuntu4.3 & associated libraries cause HUGE memory usage on wlan0. Usage of wlan0 by any net app causes resident memory consumption by NMG to grow until all system memory is used and system becomes unresponsive. + This takes several hours, but is consistent and unavoidable. Reverting to previous version of NMG (0.9.8.8-0ubuntu4.2) eliminates the issue and NMG functions as expected. Xubuntu 14.04 LTS up-to-date AMD64 Toshiba C650D Laptop w/ Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter -- 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/1351903 Title: network-manager-gnome 0.9.8.8-0ubuntu4.3 & or associated libraries cause HUGE memory usage on wlan0 Status in “network-manager” package in Ubuntu: New Bug description: Network-manager-gnome 0.9.8.8-0ubuntu4.3 & associated libraries cause HUGE memory usage on wlan0. Usage of wlan0 by any net app causes resident memory consumption by NMG to grow until all system memory is used and system becomes unresponsive. This takes several hours, but is consistent and unavoidable. Reverting to previous version of NMG (0.9.8.8-0ubuntu4.2) eliminates the issue and NMG functions as expected. Xubuntu 14.04 LTS up-to-date AMD64 Toshiba C650D Laptop w/ Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351801] Re: lrt test found crash file _usr_bin_unity8.32011.crash
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1351801 Title: lrt test found crash file _usr_bin_unity8.32011.crash Status in LRT crashes: New Status in “unity8” package in Ubuntu: New Bug description: Summary: Crash file _usr_bin_unity8.32011.crash was found Steps to reproduce: 1. Run lrt test in lp:lrt Expected result: No crashes happen Actual result: A crash happened System info: base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/utopic-proposed build_number: 165 version_detail: ubuntu=20140801,device=20140728.1,version=165 Device=mako To manage notifications about this bug go to: https://bugs.launchpad.net/lrt-crashes/+bug/1351801/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351801] Re: lrt test found crash file _usr_bin_unity8.32011.crash
This is different than the last one.
I am not sure if this is in mir or in unity8, the stack trace is not
complete
Thread 22 (Thread 0xa250f450 (LWP 3049)):
#0 __libc_do_syscall () at
../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:43
No locals.
#1 0xb60da192 in __pthread_cond_wait (cond=0xb0f06a18, mutex=0xb0f06a00) at
pthread_cond_wait.c:187
_a2 = 128
_nametmp = 240
_a3tmp = 13
_a3 = 13
_a1 = -1326421476
_a4tmp = 0
_a4 = 0
_name = 240
__ret =
futex_val = 13
buffer = {__routine = 0xb60d9f6d <__condvar_cleanup>, __arg =
0xa250ed80, __canceltype = 0, __prev = 0x0}
cbuffer = {oldtype = 0, cond = 0xb0f06a18, mutex = 0xb0f06a00, bc_seq
= 6}
err =
pshared = 0
pi_flag = 0
val =
seq = 6
#2 0xb63908b4 in std::condition_variable::wait(std::unique_lock&)
() from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
No symbol table info available.
#3 0xab6619ca in ?? () from /usr/lib/arm-linux-gnueabihf/libunity-scopes.so.2
No symbol table info available.
#4 0xab65e97e in
unity::scopes::internal::RuntimeImpl::waiter_thread(std::shared_ptr
> > const&) const () from /usr/lib/arm-linux-gnueabihf/libunity-scopes.so.2
No symbol table info available.
#5 0xb6393490 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
No symbol table info available.
#6 0xb60d6f98 in start_thread (arg=0xa250f450) at pthread_create.c:311
pd = 0xa250f450
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1571752344, -1571752880,
0, -1571754416, -1571754096, -1571752316, 0, -1529679528, 346834241, 1588,
0 }, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0,
0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
pagesize_m1 =
sp =
freesize =
__PRETTY_FUNCTION__ = "start_thread"
#7 0xb628d7cc in ?? () at
../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92 from
/lib/arm-linux-gnueabihf/libc.so.6
No locals.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
.
--
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/1351801
Title:
lrt test found crash file _usr_bin_unity8.32011.crash
Status in LRT crashes:
New
Status in “unity8” package in Ubuntu:
New
Bug description:
Summary:
Crash file _usr_bin_unity8.32011.crash was found
Steps to reproduce:
1. Run lrt test in lp:lrt
Expected result:
No crashes happen
Actual result:
A crash happened
System info:
base: system-image.ubuntu.com
http_port: 80
https_port: 443
channel: ubuntu-touch/utopic-proposed
build_number: 165
version_detail: ubuntu=20140801,device=20140728.1,version=165
Device=mako
To manage notifications about this bug go to:
https://bugs.launchpad.net/lrt-crashes/+bug/1351801/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351801] Re: lrt test found crash file _usr_bin_unity8.32011.crash
Thread 7 (Thread 0xb19eb450 (LWP 2773)):
#0 0xb628dcc2 in epoll_wait () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1 0xb3d17750 in android::Looper::pollInner(int) () from
/usr/lib/arm-linux-gnueabihf/libmirclient.so.8
No symbol table info available.
#2 0xb3d17aa0 in android::Looper::pollOnce(int, int*, int*, void**) () from
/usr/lib/arm-linux-gnueabihf/libmirclient.so.8
No symbol table info available.
#3 0xb3fb6ece in
mir::input::receiver::android::InputReceiver::next_event(std::chrono::duration > const&, MirEvent&) () from
/usr/lib/arm-linux-gnueabihf/libmirserver.so.23
No symbol table info available.
#4 0xb3fb792c in
mir::input::receiver::android::InputReceiverThread::thread_loop() () from
/usr/lib/arm-linux-gnueabihf/libmirserver.so.23
No symbol table info available.
#5 0xb6393490 in ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
No symbol table info available.
#6 0xb60d6f98 in start_thread (arg=0xb19eb450) at pthread_create.c:311
pd = 0xb19eb450
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1314998680, -1314999216,
0, -1315000752, -1315000432, -1314998652, 0, -1093673208, 123864385, 1588,
0 }, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0,
0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = 0
pagesize_m1 =
sp =
freesize =
__PRETTY_FUNCTION__ = "start_thread"
#7 0xb628d7cc in ?? () at
../ports/sysdeps/unix/sysv/linux/arm/nptl/../clone.S:92 from
/lib/arm-linux-gnueabihf/libc.so.6
No locals.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
--
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/1351801
Title:
lrt test found crash file _usr_bin_unity8.32011.crash
Status in LRT crashes:
New
Status in “unity8” package in Ubuntu:
New
Bug description:
Summary:
Crash file _usr_bin_unity8.32011.crash was found
Steps to reproduce:
1. Run lrt test in lp:lrt
Expected result:
No crashes happen
Actual result:
A crash happened
System info:
base: system-image.ubuntu.com
http_port: 80
https_port: 443
channel: ubuntu-touch/utopic-proposed
build_number: 165
version_detail: ubuntu=20140801,device=20140728.1,version=165
Device=mako
To manage notifications about this bug go to:
https://bugs.launchpad.net/lrt-crashes/+bug/1351801/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
