[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot
I've compared the schematics of w230st and w230ss from the service manuals and the codec is exactly the same, but the w230ss has an additional chip between the codec and the headphone jack. The manual says that it's an pre-amp but doesn't mention the exact model. The pre- amp is connected to the SMBus, I guess it needs initialization after standby. The service manual also has photos of the motherboard, unfortunately they are low-res and it's not possible to identify the chip. -- 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 fresh boot Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: When I boot Windows and then reboot into Ubuntu the sound is ok. But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. Also heaphone stop working after putting laptop to sleep. 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 1174706] Re: Unable to set Alt+Print as screenshot keyboard shortcut (laptopt keyboard)
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/1174706 Title: Unable to set Alt+Print as screenshot keyboard shortcut (laptopt keyboard) Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: On 13.04, under System Settings - Keyboard - Shortcuts - Screenshots - Take a screenshot of a window, I am unable to set Alt + Print as the shortcut. Pressing that combination causes Mod2 + Alt L to be (incorrectly) set. NB I am able to set 'Print' as the shortcut key for Take full screenshot, it is only in combination with the Alt key that I am unable to set the shortcut. Also, this is on a laptop keyboard (HP G61 laptop), so Print Screen is accessed by 'Fn' key + Home key, so the actual key combination I want to use is 'Fn' + Alt + Home. My scan codes for the keys, if it helps (sudo /lib/udev/keymap -i input/event4 ~/keymap.log): Alt L: scan code: 0x38 key code: leftalt Home: scan code: 0xC7 key code: home 'Fn' + Home: scan code: 0xB7 key code: sysrq 'Fn' + Alt L + Home scan code: 0x38 key code: leftalt scan code: 0x54 key code: sysrq Ah, just to complicate matters further, 'Fn' + End also gives: scan code: 0x54 key code: sysrq Further info - I am trying to reset the shortcuts back to the defaults, i.e. they did originally work with Print = full screenshot and Alt Print = window screenshot, I was messing around with trying to use Shutter instead, decided I didn't like it, and now am trying to set the shortcuts back to the defaults. Further further info, I have a sort of workaround by using CCSM keybindings for Alt+Print bound to gnome-screenshot --window, which I feel is less than ideal (although it at least does what I want!). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1174706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349100] [NEW] 3G modem e176g issue
You have been subscribed to a public bug: System name: ubuntu 14.04 64 bit. installed releases: ii libmm-glib0:amd64 1.0.0-2ubuntu1 amd64D-Bus service for managing modems - shared libraries ii modemmanager 1.0.0-2ubuntu1 amd64D-Bus service for managing modems ii network-manager 0.9.8.8-0ubuntu7 amd64network management framework (daemon and userspace tools) ii network-manager-gnome 0.9.8.8-0ubuntu4.2 amd64network management framework (GNOME frontend) ii network-manager-openvpn 0.9.8.2-1ubuntu4 amd64network management framework (OpenVPN plugin core) ii network-manager-openvpn-gnome 0.9.8.2-1ubuntu4 amd64network management framework (OpenVPN plugin GNOME GUI) ii network-manager-pptp 0.9.8.2-1ubuntu2 amd64network management framework (PPTP plugin core) ii network-manager-pptp-gnome0.9.8.2-1ubuntu2 amd64network management framework (PPTP plugin GNOME GUI) ii network-manager-vpnc 0.9.8.6-1ubuntu2 amd64network management framework (VPNC plugin core) ii network-manager-vpnc-gnome0.9.8.6-1ubuntu2 amd64network management framework (VPNC plugin GNOME GUI) Modem can not be initialized by using modem manager. wvdial option is working for the modem. In the wvdial conf modem port seems as /dev/ttyUSB0 (working port) according to trial but in modemmanager gui it seems as /dev/ttyUSB1 Working wvdial.conf: [Dialer 3g] Init2 = AT+CGDCONT=1,IP,mgb Modem Type = Analog Modem Baud = 115200 New PPPD = yes Modem = /dev/ttyUSB0 ISDN = 0 Phone = *99# Password = internet Username = internet Auto DNS =1 [Dialer pin] Modem = /dev/ttyUSB0 Baud = 115200 Init2 = AT+CGDCONT=1,IP,mgb == nm-tool output: - Device: ttyUSB1 -- Type: Mobile Broadband (GSM) Driver:option1 State: disconnected Default: no Capabilities: = /var/log/syslog output during trying to make connection using network-manager: Jul 27 15:46:10 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled - enabling) Jul 27 15:46:10 ahmetyhp NetworkManager[1286]: info (ttyUSB1) modem state changed, 'disabled' -- 'enabling' (reason: user-requested) Jul 27 15:46:10 ahmetyhp ModemManager[939]: warn (ttyUSB1): port attributes not fully set Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown - registering) Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering - home) Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '286', MNC: '1', Location area code: '0', Cell ID: '0') Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling - registered) Jul 27 15:46:11 ahmetyhp NetworkManager[1286]: info (ttyUSB1) modem state changed, 'enabling' -- 'registered' (reason: user-requested) Jul 27 15:46:11 ahmetyhp NetworkManager[1286]: info WWAN now enabled by management service Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (40) Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown - umts) Jul 27 15:46:27 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (29) Jul 27 15:46:31 ahmetyhp NetworkManager[1286]: info Activation (ttyUSB1) starting connection 'Turkcell' Jul 27 15:46:31 ahmetyhp NetworkManager[1286]: info (ttyUSB1): device state change: disconnected - prepare (reason 'none') [30 40 0] Jul 27 15:46:31 ahmetyhp NetworkManager[1286]: info NetworkManager state is now CONNECTING Jul 27 15:46:31 ahmetyhp NetworkManager[1286]: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled... Jul 27 15:46:31 ahmetyhp NetworkManager[1286]: info Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started... Jul 27 15:46:31 ahmetyhp NetworkManager[1286]: info
[Touch-packages] [Bug 1349106] [NEW] Shift+AltGr is not mapped to the Compose key
Public bug reported: They Compose Key documentation says: https://help.ubuntu.com/community/ComposeKey ... 4. From [Layouts] tab click Options... (or Layout Options... pre 10.04) 5. Expand the listing of Compose key position options [+]. 6. if no box is ticked then the Shift+AltGr (Right Alt Key) is the Compose key (also called the Multi_Key in Xwindow documentation). I have Ubuntu 14.04 64 bit but Shift+AltGr does not work as Compose key (I have tried both left and right Shift). I have tested this both with the English (US) and Czech (qwerty) keyboards. In System Settings Keyboard Shortcuts Typing if I define Compose Key to Right Ctrl or Caps Lock then it works with the selected key as expected. Below is xev otput with System Settings Keyboard Shortcuts Typing Compose Key set to Disabled. --- left Shif+AltGrt: KeyPress event, serial 37, synthetic NO, window 0x401, root 0xbf, subw 0x402, time 18394655, (41,53), root:(2201,105), state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x401, root 0xbf, subw 0x402, time 18395156, (41,53), root:(2201,105), state 0x11, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0xbf, subw 0x402, time 18395226, (41,53), root:(2201,105), state 0x91, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0xbf, subw 0x402, time 18395611, (41,53), root:(2201,105), state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False --- --- right Shift+AltGr: KeyPress event, serial 37, synthetic NO, window 0x401, root 0xbf, subw 0x402, time 18485471, (22,46), root:(2182,98), state 0x10, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyPress event, serial 37, synthetic NO, window 0x401, root 0xbf, subw 0x402, time 18485864, (22,46), root:(2182,98), state 0x11, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0xbf, subw 0x402, time 18486033, (22,46), root:(2182,98), state 0x91, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0xbf, subw 0x402, time 18486373, (22,46), root:(2182,98), state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False --- Working compose key mapping (e.g. on right Ctrl) shows the compose key keysym as Multi_key. 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 Jul 27 15:05:40 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2211] NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2211] InstallationDate: Installed on 2014-07-18 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 20BE005YMC 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: 05/15/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GMET65WW (2.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BE005YMC dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No
[Touch-packages] [Bug 1349100] Re: 3G modem e176g issue
** Project changed: launchpad = modemmanager (Ubuntu) ** Package changed: modemmanager (Ubuntu) = modemmanager -- 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/1349100 Title: 3G modem e176g issue Status in ModemManager (with NetworkManager support): New Bug description: System name: ubuntu 14.04 64 bit. installed releases: ii libmm-glib0:amd64 1.0.0-2ubuntu1 amd64D-Bus service for managing modems - shared libraries ii modemmanager 1.0.0-2ubuntu1 amd64D-Bus service for managing modems ii network-manager 0.9.8.8-0ubuntu7 amd64network management framework (daemon and userspace tools) ii network-manager-gnome 0.9.8.8-0ubuntu4.2 amd64network management framework (GNOME frontend) ii network-manager-openvpn 0.9.8.2-1ubuntu4 amd64network management framework (OpenVPN plugin core) ii network-manager-openvpn-gnome 0.9.8.2-1ubuntu4 amd64network management framework (OpenVPN plugin GNOME GUI) ii network-manager-pptp 0.9.8.2-1ubuntu2 amd64network management framework (PPTP plugin core) ii network-manager-pptp-gnome0.9.8.2-1ubuntu2 amd64network management framework (PPTP plugin GNOME GUI) ii network-manager-vpnc 0.9.8.6-1ubuntu2 amd64network management framework (VPNC plugin core) ii network-manager-vpnc-gnome0.9.8.6-1ubuntu2 amd64network management framework (VPNC plugin GNOME GUI) Modem can not be initialized by using modem manager. wvdial option is working for the modem. In the wvdial conf modem port seems as /dev/ttyUSB0 (working port) according to trial but in modemmanager gui it seems as /dev/ttyUSB1 Working wvdial.conf: [Dialer 3g] Init2 = AT+CGDCONT=1,IP,mgb Modem Type = Analog Modem Baud = 115200 New PPPD = yes Modem = /dev/ttyUSB0 ISDN = 0 Phone = *99# Password = internet Username = internet Auto DNS =1 [Dialer pin] Modem = /dev/ttyUSB0 Baud = 115200 Init2 = AT+CGDCONT=1,IP,mgb == nm-tool output: - Device: ttyUSB1 -- Type: Mobile Broadband (GSM) Driver:option1 State: disconnected Default: no Capabilities: = /var/log/syslog output during trying to make connection using network-manager: Jul 27 15:46:10 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled - enabling) Jul 27 15:46:10 ahmetyhp NetworkManager[1286]: info (ttyUSB1) modem state changed, 'disabled' -- 'enabling' (reason: user-requested) Jul 27 15:46:10 ahmetyhp ModemManager[939]: warn (ttyUSB1): port attributes not fully set Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown - registering) Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering - home) Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '286', MNC: '1', Location area code: '0', Cell ID: '0') Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling - registered) Jul 27 15:46:11 ahmetyhp NetworkManager[1286]: info (ttyUSB1) modem state changed, 'enabling' -- 'registered' (reason: user-requested) Jul 27 15:46:11 ahmetyhp NetworkManager[1286]: info WWAN now enabled by management service Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (40) Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown - umts) Jul 27 15:46:27 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (29) Jul 27 15:46:31 ahmetyhp NetworkManager[1286]: info Activation (ttyUSB1) starting connection 'Turkcell' Jul 27 15:46:31 ahmetyhp
[Touch-packages] [Bug 1348393] Re: OpenAL 1.15.x Breaks Multiarch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openal-soft (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openal-soft in Ubuntu. https://bugs.launchpad.net/bugs/1348393 Title: OpenAL 1.15.x Breaks Multiarch Status in “openal-soft” package in Ubuntu: Confirmed Status in “roaraudio” package in Ubuntu: Triaged Status in “roaraudio” package in Debian: New Bug description: When 1 install's OpenAL which was a resent upgrade it removes a program called wine and after it is done installed if you try to reinstall Wine it says its broken. When ya remove Open-AL and reinstall Wine it wants to remove the entire Ubuntu Desktop components that make it. theres a History log of Upgrade progress below --- ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 2279 F pulseaudio /dev/snd/controlC0: darkangel 2279 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=a22cc369-bf57-44d6-88c0-2de766873fd6 InstallationDate: Installed on 2014-07-20 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: eMachines EL1360G NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 RelatedPackageVersions: linux-restricted-modules-3.16.0-5-generic N/A linux-backports-modules-3.16.0-5-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/1348393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304708] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()
** 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1304708 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() Status in “ibus” package in Ubuntu: New Bug description: ibus crashes in normal operation condition without any indications. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 8 23:13:09 2014 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2014-03-18 (20 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140318) ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1304708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289267] Re: ibus-daemon crashed with SIGSEGV in invoke_set_property_in_idle_cb()
** 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1289267 Title: ibus-daemon crashed with SIGSEGV in invoke_set_property_in_idle_cb() Status in “ibus” package in Ubuntu: New Bug description: dont know ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: Unity Date: Fri Mar 7 11:32:37 2014 Disassembly: = 0x10: Cannot access memory at address 0x10 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2014-03-03 (3 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140204) ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x10: Cannot access memory at address 0x10 PC (0x0010) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: ibus-daemon crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to trusty on 2014-03-03 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1289267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1303089] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message()
** 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1303089 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() Status in “ibus” package in Ubuntu: New Bug description: Sorry, not sure about how the error occurred. Didn't use the system since the last boot one hour ago. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 5 17:29:31 2014 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2014-01-25 (70 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121.1) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message() 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/ibus/+bug/1303089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1236456] Re: ibus-daemon crashed with SIGSEGV in __find_specmb()
** 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1236456 Title: ibus-daemon crashed with SIGSEGV in __find_specmb() Status in “ibus” package in Ubuntu: New Bug description: Curious error suddenly appearing, with no apparent effect on the program I was using (Firefox, Texmaker, Terminal and Nautilus). ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 18:26:06 2013 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2013-07-18 (80 days ago) InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True ProcCmdline: /usr/bin/ibus-daemon --replace --xim --panel disable ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=fr_FR LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0x7f4eede1581a _IO_vfprintf_internal+154:callq 0x7f4eede5fb20 strchrnul PC (0x7f4eede1581a) ok source 0x7f4eede5fb20 (0x7f4eede5fb20) ok destination (%rsp) (0x7f4eeb394f50) in non-writable VMA region: 0x7f4eeb394000-0x7f4eeb395000 ---p None Stack memory exhausted (SP below stack segment) SegvReason: writing VMA None Signal: 11 SourcePackage: ibus StacktraceTop: __find_specmb (format=0x7f4eeec6ae68 (%s)) at printf-parse.h:109 _IO_vfprintf_internal (s=s@entry=0x7f4eeb3955a0, format=format@entry=0x7f4eeec6ae68 (%s), ap=ap@entry=0x7f4eeb395708) at vfprintf.c:1326 __GI___vasprintf_chk (result_ptr=0x7f4eeb3956e8, flags=1, format=0x7f4eeec6ae68 (%s), args=0x7f4eeb395708) 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 Title: ibus-daemon crashed with SIGSEGV in __find_specmb() UpgradeStatus: Upgraded to saucy on 2013-07-29 (69 days ago) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1236456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290282] Re: main.py crashed with SIGSEGV in gdk_window_get_events()
** 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1290282 Title: main.py crashed with SIGSEGV in gdk_window_get_events() Status in “ibus” package in Ubuntu: New Bug description: ibus fails to open. Kubuntu 14.04 ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: KDE Date: Mon Mar 10 18:26:52 2014 ExecutablePath: /usr/share/ibus/setup/main.py InstallationDate: Installed on 2014-03-10 (0 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140227) InterpreterPath: /usr/bin/python2.7 ProcCmdline: /usr/bin/python /usr/share/ibus/setup/main.py SegvAnalysis: Segfault happened at: 0x7fe9d784c024 gdk_window_get_events+84: mov %al,(%rax) PC (0x7fe9d784c024) ok source %al ok destination (%rax) (0x0001) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: ibus StacktraceTop: gdk_window_get_events () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_widget_add_events () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: main.py crashed with SIGSEGV in gdk_window_get_events() 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/ibus/+bug/1290282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 819944] Re: ibus doesn't work in nautilus
Cannot reproduce the problem, you might want to check if you have ibus selected in language-selector. ** Changed in: ibus (Ubuntu) Status: New = Invalid -- 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/819944 Title: ibus doesn't work in nautilus Status in “ibus” package in Ubuntu: Invalid Bug description: Can't rename my files. I use Ibus to input chinese, and when I need to create/rename a folder, ibus doesn't activate... so I can't use chinese. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/819944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1237231] Re: ibus-daemon crashed with SIGABRT in _g_log_abort()
** 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1237231 Title: ibus-daemon crashed with SIGABRT in _g_log_abort() Status in “ibus” package in Ubuntu: New Bug description: The error happens soon after logging in without any user action. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Tue Oct 8 15:20:46 2013 ExecutablePath: /usr/bin/ibus-daemon MarkForUpload: True ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: ibus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_list_find_custom () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to saucy on 2012-05-18 (508 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1237231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 959174] Re: ibus-daemon crashed with SIGSEGV in g_dbus_is_name()
** 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/959174 Title: ibus-daemon crashed with SIGSEGV in g_dbus_is_name() Status in “ibus” package in Ubuntu: New Bug description: Regularly working with some windows open. No idea what caused the bug. One possible reason is that I was using LyX (a qt program) and ibus might have crashed because of that. The system is set for the brazilian portuguese language and I live in Korea, so I have to use Korean and, sometimes, Japanese and Chinese on top of that. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: ibus 1.4.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11 Uname: Linux 3.2.0-19-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 19 19:38:40 2012 ExecutablePath: /usr/bin/ibus-daemon InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) ProcCmdline: /usr/bin/ibus-daemon --xim SegvAnalysis: Segfault happened at: 0xb73552b6:movdqu (%edi),%xmm1 PC (0xb73552b6) ok source (%edi) (0x) not located in a known VMA region (needed readable region)! destination %xmm1 ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 g_dbus_is_name () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 g_dbus_message_set_sender () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGSEGV in g_dbus_is_name() UpgradeStatus: Upgraded to precise on 2012-02-23 (24 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/959174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1259728] Re: ibus-setup dialog has unusable layout
** Changed in: ibus (Ubuntu) Status: Incomplete = Fix Released -- 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/1259728 Title: ibus-setup dialog has unusable layout Status in “ibus” package in Ubuntu: Fix Released Bug description: The ibus preferences dialog for selecting a shortcut contains a list that is too narrow. It is impossible to read the selected list item or what else is in the list. Resizing the dialog does not stretch the list or spread the widgets equally over the available space (see image after resizing the dialog). Besides that, the widgets lack padding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1259728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1258778] Re: IBus input candidates not shown in GNOME Fallback session
** Changed in: ibus (Ubuntu) Status: New = Fix Released -- 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/1258778 Title: IBus input candidates not shown in GNOME Fallback session Status in “ibus” package in Ubuntu: Fix Released Bug description: I was able to add Chinese (Pinyin) as input method in Ubuntu 13.10's new Text Entry Settings. Switching between English (US) and Chinese entry works for me, generally. When I'm using the Ubuntu (Default) (Unity) session, input candidates are also properly shown (a little floating window that shows candidate Chinese characters while typing). However, when I use the GNOME Fallback or GNOME with Xmonad session, as I normally do, the candidates do not show up at all. This makes Pinyin input useless. OS and package versions: ke@apis:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 ke@apis:~$ apt-cache policy ibus ibus: Installed: 1.5.3-6ubuntu2 Candidate: 1.5.3-6ubuntu2 Version table: *** 1.5.3-6ubuntu2 0 500 http://nl.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1258778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1244554] Re: Digits 1-8 don't work in the Hebrew (lyx) input source
** Package changed: ibus (Ubuntu) = gnome-settings-daemon (Ubuntu) -- 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/1244554 Title: Digits 1-8 don't work in the Hebrew (lyx) input source Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Worked find under Raring. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 25 10:17:41 2013 InstallationDate: Installed on 2012-05-29 (513 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: ibus UpgradeStatus: Upgraded to saucy on 2013-10-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1244554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295603] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()
** 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1295603 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() Status in “ibus” package in Ubuntu: New Bug description: Seems related to other bugs of similar nature (#1048161, #1252666, #1266970) although in my case this happend while being logged in KDE. It was either when I've put my computer in sleep state through closing the lid or when I powered it back on (wakeup). At wake-up time the crash window notifier was already there when I unlocked my session. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Thu Mar 20 20:05:42 2014 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2014-03-16 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140315) ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() 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/ibus/+bug/1295603/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 fresh boot
Hi Kiril, maybe you can update the title / description of the bug report, that way anybody knows what's what without reading all the comments. -- 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 fresh boot Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: When I boot Windows and then reboot into Ubuntu the sound is ok. But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. Also heaphone stop working after putting laptop to sleep. 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 1349106] Re: Shift+AltGr is not mapped to the Compose key
** Description changed: They Compose Key documentation says: https://help.ubuntu.com/community/ComposeKey ... 4. From [Layouts] tab click Options... (or Layout Options... pre 10.04) 5. Expand the listing of Compose key position options [+]. - 6. if no box is ticked then the Shift+AltGr (Right Alt Key) is the Compose key (also called the Multi_Key in Xwindow documentation). + 6. if no box is ticked then the Shift+AltGr (Right Alt Key) is the Compose key (also called the Multi_Key in Xwindow documentation). I have Ubuntu 14.04 64 bit but Shift+AltGr does not work as Compose key (I have tried both left and right Shift). I have tested this both with the English (US) and Czech (qwerty) keyboards. + xkbprint :0 command shows for the keycode 108 (the AltGr key): + - in English (US) layout: Alt_R / with Shift: Meta_R + - in Czech (qwerty) layout: ISO_Level3_Shift (both without and with Shift) + Those keysyms show in xev. + In System Settings Keyboard Shortcuts Typing if I define Compose Key to Right Ctrl or Caps Lock then it works with the selected key as - expected. + expected. The selected key has keysym Multi_key in xkbprint. - Below is xev otput with System Settings Keyboard Shortcuts Typing - Compose Key set to Disabled. - - --- left Shif+AltGrt: - KeyPress event, serial 37, synthetic NO, window 0x401, - root 0xbf, subw 0x402, time 18394655, (41,53), root:(2201,105), - state 0x10, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, - XLookupString gives 0 bytes: - XmbLookupString gives 0 bytes: - XFilterEvent returns: False - - KeyPress event, serial 37, synthetic NO, window 0x401, - root 0xbf, subw 0x402, time 18395156, (41,53), root:(2201,105), - state 0x11, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, - XKeysymToKeycode returns keycode: 92 - XLookupString gives 0 bytes: - XmbLookupString gives 0 bytes: - XFilterEvent returns: False - - KeyRelease event, serial 37, synthetic NO, window 0x401, - root 0xbf, subw 0x402, time 18395226, (41,53), root:(2201,105), - state 0x91, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, - XKeysymToKeycode returns keycode: 92 - XLookupString gives 0 bytes: - XFilterEvent returns: False - - KeyRelease event, serial 37, synthetic NO, window 0x401, - root 0xbf, subw 0x402, time 18395611, (41,53), root:(2201,105), - state 0x11, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES, - XLookupString gives 0 bytes: - XFilterEvent returns: False - --- - - --- right Shift+AltGr: - KeyPress event, serial 37, synthetic NO, window 0x401, - root 0xbf, subw 0x402, time 18485471, (22,46), root:(2182,98), - state 0x10, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, - XLookupString gives 0 bytes: - XmbLookupString gives 0 bytes: - XFilterEvent returns: False - - KeyPress event, serial 37, synthetic NO, window 0x401, - root 0xbf, subw 0x402, time 18485864, (22,46), root:(2182,98), - state 0x11, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, - XKeysymToKeycode returns keycode: 92 - XLookupString gives 0 bytes: - XmbLookupString gives 0 bytes: - XFilterEvent returns: False - - KeyRelease event, serial 37, synthetic NO, window 0x401, - root 0xbf, subw 0x402, time 18486033, (22,46), root:(2182,98), - state 0x91, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, - XKeysymToKeycode returns keycode: 92 - XLookupString gives 0 bytes: - XFilterEvent returns: False - - KeyRelease event, serial 37, synthetic NO, window 0x401, - root 0xbf, subw 0x402, time 18486373, (22,46), root:(2182,98), - state 0x11, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, - XLookupString gives 0 bytes: - XFilterEvent returns: False - --- - - Working compose key mapping (e.g. on right Ctrl) shows the compose key - keysym as Multi_key. 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 Jul 27 15:05:40 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:2211] - NVIDIA Corporation GK208M [GeForce GT 730M] [10de:1290] (rev a1) (prog-if 00 [VGA
[Touch-packages] [Bug 991004] Re: Replace libusb-0.1 with libusb-compat-0.1
** Bug watch added: Debian Bug tracker #731424 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731424 ** Also affects: libusb via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731424 Importance: Unknown Status: Unknown ** No longer affects: libusb ** Also affects: libusb (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731424 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/991004 Title: Replace libusb-0.1 with libusb-compat-0.1 Status in “libusb” package in Ubuntu: Confirmed Status in “libusb” package in Debian: Unknown Bug description: See http://www.libusb.org/wiki/libusb-compat-0.1 From http://www.libusb.org/: However, if you have installed libusb-1.0 then we strongly recommend to use libusb-compat-0.1 instead of the ancient libusb-0.1 code, so that programs which use both the 0.1 API and the 1.0 API in different parts of the program, or in different libraries used by the program, will both end up using libusb-1.0 for actual device access. This is important to avoid potential conflicts between libusb-1.0 and libusb-0.1 being used by the same process. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libusb-0.1-4 2:0.1.12-20 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sun Apr 29 12:23:48 2012 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=xterm PATH=(custom, user) LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: libusb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb/+bug/991004/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 fresh boot
Done. ** Description changed: - When I boot Windows and then reboot into Ubuntu the sound is ok. - But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. - Also heaphone stop working after putting laptop to sleep. + 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 + 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 + 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 ** Summary changed: - [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot + [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume -- 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
[Touch-packages] [Bug 1090944] Re: please change to libusbx 1.14
As of 2014.01.26, libusbx has been fully merged back into libusb and is being discontinued. ** Changed in: libusb (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1090944 Title: please change to libusbx 1.14 Status in “libusb” package in Ubuntu: Invalid Bug description: wishlist: please change to libusbx 1.14 .. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libusb-0.1-4 2:0.1.12-23 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Sun Dec 16 17:45:02 2012 InstallationDate: Installed on 2012-01-25 (325 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libusb UpgradeStatus: Upgraded to quantal on 2012-09-17 (90 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb/+bug/1090944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349121] Re: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01)
** Summary changed: - Non-existent display detected using nouveau driver + Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01) -- 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/1349121 Title: Non-existent display detected using nouveau driver (Samsung Laptop Nvidia GeForce GT 520M) (Ubuntu 14.04.01) Status in “xorg” package in Ubuntu: New Bug description: Samsung NP300V3A (Laptop) | Nvidia GF119M [GeForce GT 520M] | Ubuntu 14.04.01 LTS Xorg 1:7.7+1ubuntu8 | ubuntu-drivers-common 1:0.2.91.5 | xserver-xorg- video-nouveau 1:1.0.10-1ubuntu2 Unexpected 'ghost' display appears in settings when no extra display is connected. There is a non-existing display detected, known as Unknown Display. The bug is all in all very similar, if not a duplicate, of bug #1296020. However, as I am using Nouveau rather than Nvidia-331 and have different hardware, I thought it better to make a new report. The bug renders GDM impossible to use while Lightdm works. When logging in to Gnome Shell, the screen goes black from time to time (upon loading the shell), this I can solve by using the laptop hardware keys for switching video output. I tried the proprietary drivers and the fix committed to trusty- proposed due to bug #1296020 (ubuntu-drivers-common 1:0.2.91.6) with no avail. It seems that whatever solved the issue for a non-existing display for Nvidia-331 users is not causing the problem for those who are using Nouveau. My 'xrandr -q' output Screen 0: minimum 320 x 200, current 2390 x 768, maximum 32767 x 32767 LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) DP1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) VGA-1-2 connected 1024x768+1366+0 0mm x 0mm 1024x768 60.0* 800x60060.3 56.2 848x48060.0 640x48059.9 1024x768 (0x43) 65.0MHz h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x44) 40.0MHz h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 800x600 (0x45) 36.0MHz h: width 800 start 824 end 896 total 1024 skew0 clock 35.2KHz v: height 600 start 601 end 603 total 625 clock 56.2Hz 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: None CurrentDesktop: GNOME Date: Sun Jul 27 16:07:03 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0b6] Subsystem: Samsung Electronics Co Ltd Device [144d:c0b6] InstallationDate: Installed on 2014-07-26 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 2232:1008 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: SAMSUNG ELECTRONICS CO., LTD. 300V3A/300V4A/300V5A/200A4B/200A5B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro video=VGA-0:d quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2011 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 04FI dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 300V3A/300V4A/300V5A/200A4B/200A5B dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset
[Touch-packages] [Bug 1348393] Re: OpenAL 1.15.x Breaks Multiarch (makes 32-bit wine uninstallable on 64-bit system)
** Summary changed: - OpenAL 1.15.x Breaks Multiarch + OpenAL 1.15.x Breaks Multiarch (makes 32-bit wine uninstallable on 64-bit system) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openal-soft in Ubuntu. https://bugs.launchpad.net/bugs/1348393 Title: OpenAL 1.15.x Breaks Multiarch (makes 32-bit wine uninstallable on 64-bit system) Status in “openal-soft” package in Ubuntu: Confirmed Status in “roaraudio” package in Ubuntu: Triaged Status in “roaraudio” package in Debian: New Bug description: When 1 install's OpenAL which was a resent upgrade it removes a program called wine and after it is done installed if you try to reinstall Wine it says its broken. When ya remove Open-AL and reinstall Wine it wants to remove the entire Ubuntu Desktop components that make it. theres a History log of Upgrade progress below --- ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 2279 F pulseaudio /dev/snd/controlC0: darkangel 2279 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=a22cc369-bf57-44d6-88c0-2de766873fd6 InstallationDate: Installed on 2014-07-20 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: eMachines EL1360G NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 RelatedPackageVersions: linux-restricted-modules-3.16.0-5-generic N/A linux-backports-modules-3.16.0-5-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/1348393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313904] Re: [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after suspend/resume
I tried to investigate the preamplifier chip further but run into another bug. I'm not able to access the SMBus. When I execute modprobe i2c-i801, the following appears in the kernel log: [...] ACPI Warning: SystemIO range 0xf040-0xf05f conflicts with OpRegion 0xf040-0xf04f (\_SB_.PCI0.SBUS.SMBI) (20140214/utaddress-258) [...] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver I tried mainline kernel 3.15.6 but the problem is still present. Only found this: http://askubuntu.com/questions/449102/ubuntu-12-04-loading-i801-i2c- driver -- 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 1347605] Re: activateApplication should give a valid url for url-dispatcher
** Branch linked: lp:~unity-team/unity-scopes-shell/drop-appid- workaround -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1347605 Title: activateApplication should give a valid url for url-dispatcher Status in QML plugin for Scopes: New Status in “unity-scope-click” package in Ubuntu: Invalid Bug description: Now that we're splitting the Dash to be a separate app, activateApplication() needs to call url-dispatcher instead of directly interacting with unity's ApplicationManager. For that it would be required to change the parameter of activateApplication to give a fully qualified url that works with url-dispatcher. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scopes-shell/+bug/1347605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347605] Re: activateApplication should give a valid url for url-dispatcher
** Changed in: unity-scope-click (Ubuntu) Status: New = Invalid ** Also affects: unity-scopes-shell Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1347605 Title: activateApplication should give a valid url for url-dispatcher Status in QML plugin for Scopes: New Status in “unity-scope-click” package in Ubuntu: Invalid Bug description: Now that we're splitting the Dash to be a separate app, activateApplication() needs to call url-dispatcher instead of directly interacting with unity's ApplicationManager. For that it would be required to change the parameter of activateApplication to give a fully qualified url that works with url-dispatcher. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scopes-shell/+bug/1347605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 746383]
Tracking pango issue here: https://bugzilla.gnome.org/show_bug.cgi?id=733764 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/746383 Title: fontconfig confuses bold and medium weights Status in Fontconfig - Font Configuration Library: Fix Released Status in Pango - Layout and Text Rendering LIbrary: Fix Released Status in “fontconfig” package in Ubuntu: Triaged Status in “pango” package in Ubuntu: Triaged Bug description: Attempts to set Ubuntu Bold in the Appearance settings fall back to Ubuntu Medium. In fact, in the font selection screen there seems to be no difference between bold and medium. Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is* installed and accessible. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Thu Mar 31 08:33:44 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 746383]
My bad, this *is* a fontconfig issue. Investigating. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/746383 Title: fontconfig confuses bold and medium weights Status in Fontconfig - Font Configuration Library: Fix Released Status in Pango - Layout and Text Rendering LIbrary: Fix Released Status in “fontconfig” package in Ubuntu: Triaged Status in “pango” package in Ubuntu: Triaged Bug description: Attempts to set Ubuntu Bold in the Appearance settings fall back to Ubuntu Medium. In fact, in the font selection screen there seems to be no difference between bold and medium. Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is* installed and accessible. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Thu Mar 31 08:33:44 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 746383]
Pango fixed. See screenshots here: https://bugzilla.gnome.org/show_bug.cgi?id=733764 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/746383 Title: fontconfig confuses bold and medium weights Status in Fontconfig - Font Configuration Library: Fix Released Status in Pango - Layout and Text Rendering LIbrary: Fix Released Status in “fontconfig” package in Ubuntu: Triaged Status in “pango” package in Ubuntu: Triaged Bug description: Attempts to set Ubuntu Bold in the Appearance settings fall back to Ubuntu Medium. In fact, in the font selection screen there seems to be no difference between bold and medium. Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is* installed and accessible. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Thu Mar 31 08:33:44 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 746383] Re: fontconfig confuses bold and medium weights
** Changed in: fontconfig Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/746383 Title: fontconfig confuses bold and medium weights Status in Fontconfig - Font Configuration Library: Fix Released Status in Pango - Layout and Text Rendering LIbrary: Fix Released Status in “fontconfig” package in Ubuntu: Triaged Status in “pango” package in Ubuntu: Triaged Bug description: Attempts to set Ubuntu Bold in the Appearance settings fall back to Ubuntu Medium. In fact, in the font selection screen there seems to be no difference between bold and medium. Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is* installed and accessible. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Thu Mar 31 08:33:44 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349128] [NEW] Ubuntu 14.04 login screen doesn't accept keyboard input
You have been subscribed to a public bug: Ubuntu 14.04 login screen doesn't accept keyboard input in the password box after my system has resumed from a sleep (=lid opening), so I can't relogin anymore Excpected behaviour: the login screen should accept keyboard input and show them as stars in the password box. Workaround: click on switch user in the upper right corner, after which keyboard input is accepted again. $ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 System is fully updated. Problem started to happen one or two weeks ago, so around mid July 2014. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 14.04 login screen doesn't accept keyboard input https://bugs.launchpad.net/bugs/1349128 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input
** Package changed: ubuntu = lightdm (Ubuntu) -- 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/1349128 Title: Ubuntu 14.04 login screen doesn't accept keyboard input Status in “lightdm” package in Ubuntu: New Bug description: Ubuntu 14.04 login screen doesn't accept keyboard input in the password box after my system has resumed from a sleep (=lid opening), so I can't relogin anymore Excpected behaviour: the login screen should accept keyboard input and show them as stars in the password box. Workaround: click on switch user in the upper right corner, after which keyboard input is accepted again. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 System is fully updated. Problem started to happen one or two weeks ago, so around mid July 2014. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1349128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1215733] Re: cups config files cannot deal with symlinks and/or other filesystems
Many thanks to Peter Teuben, and for finding that the cause of the 'permission denied' actually is the symlink from /usr/share to /home. I can say the symlink also causes cups to fail in Ubuntu 14.04 (Trusty Tahr) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1215733 Title: cups config files cannot deal with symlinks and/or other filesystems Status in “cups” package in Ubuntu: Confirmed Bug description: I needed to make space on / to upgrade my ubuntu, and since /usr/share is huge (4GB in my case), decided to clone this on /home/share and let /usr/share - /home/share. I then found cups failed to work, there were messages such as Unable to open /usr/share/cups/mime: Permission denied in /var/log/cups/error_log, which eventually gave me the hint what was going on here. Also, looking at properties of a printer, the print test page button was greyed out, I could not print a test page. This turned out the easiest way for me to debug this problem (at least graphically). After the fixes (see below) and service cups restart I would see the print test page button again. To differentiate between a symlink and other-filesystem as the root cause, I decided to experiment: 1) I kept /usr/share.d and did /usr/share - /usr/share.d This failed, so this pointed to the fact that it's a symlink that was not allowed by CUPS, since /usr/share.d was on / but then it surprised me: 2) I kept /usr/share but now /usr/share/cups - /usr/share/cups.d worked, despite that it was a symlink. 3) Of course, i confirmed that /usr/share/cups - /home/cups.d indeed failed. So,other filesystem is always a fail. I'm left with this weird puzzle, why CUPS doesn't quite allow a simple symlink 1) or even 3) It seems this is against the unix philosphy and certainly burnt me and caused me a good fraction of a day of work. This could very well be a problem on apple's as well, but I have no easy access to one to test this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1215733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348757] Re: invoke-rc.d gets stuck when trying to start gnukhata-core-engine during post install
as per Petter Reinholdtsen's suggestion (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=756114#19), adding db_stop in postinst fixed this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1348757 Title: invoke-rc.d gets stuck when trying to start gnukhata-core-engine during post install Status in “sysvinit” package in Ubuntu: Invalid Status in “sysvinit” package in Debian: Unknown Bug description: I'm packaging gnukhata (http://gnukhata.org) for debian and ubuntu but I cannot start the gnukhata-core-engine service during installation on ubuntu. It works fine on debian sid (using systemd). I tried both invoke-rc.d gnukhata-core-engine start as well as service gnukhata- core-engine start. It just go defunct after it actually starts the service. I have tested on Ubuntu 12.04 and 14.04 releases. You can test it using the packages from http://people.debian.org/~praveen/gnukhata/README (currently postinst doesn not start the service, you can edit debian/gnukhata-core- engine.postinst to start the service and test) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1348757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348393] Re: OpenAL 1.15.x Breaks Multiarch (makes 32-bit wine uninstallable on 64-bit system)
Thanks for the workaround. As I haven't a clue what roaraudio is, I'll probably never need it. I have wine back again in Utopic! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openal-soft in Ubuntu. https://bugs.launchpad.net/bugs/1348393 Title: OpenAL 1.15.x Breaks Multiarch (makes 32-bit wine uninstallable on 64-bit system) Status in “openal-soft” package in Ubuntu: Confirmed Status in “roaraudio” package in Ubuntu: Triaged Status in “roaraudio” package in Debian: New Bug description: When 1 install's OpenAL which was a resent upgrade it removes a program called wine and after it is done installed if you try to reinstall Wine it says its broken. When ya remove Open-AL and reinstall Wine it wants to remove the entire Ubuntu Desktop components that make it. theres a History log of Upgrade progress below --- ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darkangel 2279 F pulseaudio /dev/snd/controlC0: darkangel 2279 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=a22cc369-bf57-44d6-88c0-2de766873fd6 InstallationDate: Installed on 2014-07-20 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. MachineType: eMachines EL1360G NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6 RelatedPackageVersions: linux-restricted-modules-3.16.0-5-generic N/A linux-backports-modules-3.16.0-5-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-5-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/16/2011 dmi.bios.vendor: AMI dmi.bios.version: P01-C1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: EL1360G dmi.board.vendor: eMachines dmi.chassis.type: 3 dmi.chassis.vendor: eMachines dmi.modalias: dmi:bvnAMI:bvrP01-C1:bd11/16/2011:svneMachines:pnEL1360G:pvr:rvneMachines:rnEL1360G:rvr:cvneMachines:ct3:cvr: dmi.product.name: EL1360G dmi.sys.vendor: eMachines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/1348393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 408719] Re: QtDbus: KIO scheduler exit handler crashes VLC
Fixed in Qt 4.8.6 according to upstream bug. ** Changed in: qt Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/408719 Title: QtDbus: KIO scheduler exit handler crashes VLC Status in kdelibs: Won't Fix Status in Qt: Fix Released Status in VLC media player: Invalid Status in “qt4-x11” package in Ubuntu: Confirmed Status in “vlc” package in Ubuntu: Invalid Status in “kde4libs” package in Debian: Fix Released Status in Fedora: New Status in “qt4-x11” package in Mandriva: Unknown Bug description: Binary package hint: vlc Description: Ubuntu karmic (development branch) Release: 9.10 On Kubuntu, VLC crashes at exit if the open file (or save file) dialog has been ever used. ProblemType: Crash Architecture: i386 Date: Tue Aug 4 08:36:19 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/vlc Package: vlc-nox 1.0.0-1ubuntu1 ProcCmdline: vlc ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SegvAnalysis: Segfault happened at: 0x5b1b846: mov0x4(%edx),%ecx PC (0x05b1b846) ok source 0x4(%edx) (0x0004) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: vlc StacktraceTop: ?? () from /usr/lib/libQtDBus.so.4 ?? () from /usr/lib/libQtDBus.so.4 QMetaObject::activate(QObject*, int, int, void**) () QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**) () from /usr/lib/libQtCore.so.4 QObject::destroyed(QObject*) () from /usr/lib/libQtCore.so.4 Title: vlc crashed with SIGSEGV in QMetaObject::activate() Uname: Linux 2.6.31-5-generic i686 UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse sambashare video To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/408719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302004] Re: Indicator-datetime still doesn't list all events for today's date (Trusty)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1302004 Title: Indicator-datetime still doesn't list all events for today's date (Trusty) Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: This bug is related to this bug: Bug #1293646 (Which is marked as fix released) With latest update of indicator (13.10.0+14.04.20140328-0ubuntu1) it lists all events for all past selected dates properly (which was fixed in bug Bug #1293646) except today's date. When I click on any past date in calendar it shows: 1. all all-day events for the day. 2. all events with time for the day 3. upcoming (future) all-day events 4. upcoming (future) events with time But when I click on today's date it only shows: 1. future all day events 2. future events with time I still have to click on previous day's date to find out all all-day events for today. The behavior (showing all events for a day) should be same for any date, including today's date. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1302004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349128] Re: Ubuntu 14.04 login screen doesn't accept keyboard input
Update: Another workaround: change the language in the upper right corner, in my case switch from En1 to En2. After that, the password box accepts keyboard input and shows corresponding dots. -- 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/1349128 Title: Ubuntu 14.04 login screen doesn't accept keyboard input Status in “lightdm” package in Ubuntu: New Bug description: Ubuntu 14.04 login screen doesn't accept keyboard input in the password box after my system has resumed from a sleep (=lid opening), so I can't relogin anymore Excpected behaviour: the login screen should accept keyboard input and show them as stars in the password box. Workaround: click on switch user in the upper right corner, after which keyboard input is accepted again. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 System is fully updated. Problem started to happen one or two weeks ago, so around mid July 2014. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1349128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 727904] Re: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken
** Changed in: unity (Ubuntu Trusty) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/727904 Title: Launcher, Window management - Switching between spreads when dragging a file over the Launcher is broken Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: Fix Committed Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “compiz” source package in Trusty: Fix Released Status in “unity” source package in Trusty: Invalid Bug description: To reproduce: Open two Chrome windows and two Firefox windows. Drag a .html file over the Chrome icon in the Launcher. A spread of the two Chrome windows should appear. Then continue the same drag, and drag the file over the Firefox icon in the Launcher. Nothing happens, the Chrome spread is still displayed. Desired behaviour; After a spread appears as a result of the user dragging a file over a application icon in the Launcher, if the user then drags the file over a different application icon (where the application is also a valid drop receptacle for the file type) the spread should switch to the newly selected application. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349100] Re: 3G modem e176g issue
** Project changed: modemmanager = modemmanager (Ubuntu) -- 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/1349100 Title: 3G modem e176g issue Status in “modemmanager” package in Ubuntu: New Bug description: System name: ubuntu 14.04 64 bit. installed releases: ii libmm-glib0:amd64 1.0.0-2ubuntu1 amd64D-Bus service for managing modems - shared libraries ii modemmanager 1.0.0-2ubuntu1 amd64D-Bus service for managing modems ii network-manager 0.9.8.8-0ubuntu7 amd64network management framework (daemon and userspace tools) ii network-manager-gnome 0.9.8.8-0ubuntu4.2 amd64network management framework (GNOME frontend) ii network-manager-openvpn 0.9.8.2-1ubuntu4 amd64network management framework (OpenVPN plugin core) ii network-manager-openvpn-gnome 0.9.8.2-1ubuntu4 amd64network management framework (OpenVPN plugin GNOME GUI) ii network-manager-pptp 0.9.8.2-1ubuntu2 amd64network management framework (PPTP plugin core) ii network-manager-pptp-gnome0.9.8.2-1ubuntu2 amd64network management framework (PPTP plugin GNOME GUI) ii network-manager-vpnc 0.9.8.6-1ubuntu2 amd64network management framework (VPNC plugin core) ii network-manager-vpnc-gnome0.9.8.6-1ubuntu2 amd64network management framework (VPNC plugin GNOME GUI) Modem can not be initialized by using modem manager. wvdial option is working for the modem. In the wvdial conf modem port seems as /dev/ttyUSB0 (working port) according to trial but in modemmanager gui it seems as /dev/ttyUSB1 Working wvdial.conf: [Dialer 3g] Init2 = AT+CGDCONT=1,IP,mgb Modem Type = Analog Modem Baud = 115200 New PPPD = yes Modem = /dev/ttyUSB0 ISDN = 0 Phone = *99# Password = internet Username = internet Auto DNS =1 [Dialer pin] Modem = /dev/ttyUSB0 Baud = 115200 Init2 = AT+CGDCONT=1,IP,mgb == nm-tool output: - Device: ttyUSB1 -- Type: Mobile Broadband (GSM) Driver:option1 State: disconnected Default: no Capabilities: = /var/log/syslog output during trying to make connection using network-manager: Jul 27 15:46:10 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled - enabling) Jul 27 15:46:10 ahmetyhp NetworkManager[1286]: info (ttyUSB1) modem state changed, 'disabled' -- 'enabling' (reason: user-requested) Jul 27 15:46:10 ahmetyhp ModemManager[939]: warn (ttyUSB1): port attributes not fully set Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown - registering) Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering - home) Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP location updated (MCC: '286', MNC: '1', Location area code: '0', Cell ID: '0') Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling - registered) Jul 27 15:46:11 ahmetyhp NetworkManager[1286]: info (ttyUSB1) modem state changed, 'enabling' -- 'registered' (reason: user-requested) Jul 27 15:46:11 ahmetyhp NetworkManager[1286]: info WWAN now enabled by management service Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (40) Jul 27 15:46:11 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown - umts) Jul 27 15:46:27 ahmetyhp ModemManager[939]: info Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (29) Jul 27 15:46:31 ahmetyhp NetworkManager[1286]: info Activation (ttyUSB1) starting connection 'Turkcell' Jul 27 15:46:31 ahmetyhp NetworkManager[1286]: info (ttyUSB1): device state change: disconnected -
[Touch-packages] [Bug 1348251] Re: please make use of pam_tally2 for Touch login and screenunlock
** Also affects: lightdm Importance: Undecided Status: New ** Changed in: lightdm Importance: Undecided = Medium ** Changed in: lightdm Status: New = Fix Committed ** Changed in: lightdm (Ubuntu) Status: Incomplete = In Progress ** Also affects: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) = Robert Ancell (robert-ancell) ** Changed in: lightdm Assignee: (unassigned) = Robert Ancell (robert-ancell) ** Changed in: lightdm Milestone: None = 1.11.5 -- 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/1348251 Title: please make use of pam_tally2 for Touch login and screenunlock Status in Light Display Manager: Fix Committed Status in “lightdm” package in Ubuntu: In Progress Status in “ubuntu-touch-session” package in Ubuntu: New Bug description: Ubuntu Touch will soon have/now has the ability to set a PIN/password for the user. If the password is set, we should provide some protection against brute force password guessing since many users will choose to use PINs rather than proper passwords. This is required for devices for RTM, but not for the traditional Ubuntu desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1348251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348251] Re: please make use of pam_tally2 for Touch login and screenunlock
** Branch linked: lp:lightdm -- 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/1348251 Title: please make use of pam_tally2 for Touch login and screenunlock Status in Light Display Manager: Fix Committed Status in “lightdm” package in Ubuntu: In Progress Status in “ubuntu-touch-session” package in Ubuntu: New Bug description: Ubuntu Touch will soon have/now has the ability to set a PIN/password for the user. If the password is set, we should provide some protection against brute force password guessing since many users will choose to use PINs rather than proper passwords. This is required for devices for RTM, but not for the traditional Ubuntu desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1348251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349203] [NEW] screen freezes
Public bug reported: When I try to click on search your computer and online sources the screen spazzes out I am using Ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jul 27 20:31:36 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30ea] InstallationDate: Installed on 2014-07-21 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 12/07/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.05 dmi.board.name: 30EA dmi.board.vendor: Quanta dmi.board.version: 86.09 dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.05:bd12/07/2007:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A: dmi.product.name: Compaq Presario F700 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Jul 27 20:22:29 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: nouveau ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1349203 Title: screen freezes Status in “unity” package in Ubuntu: New Bug description: When I try to click on search your computer and online sources the screen spazzes out I am using Ubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jul 27 20:31:36 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:30ea] InstallationDate: Installed on 2014-07-21 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
[Touch-packages] [Bug 1348251] Re: please make use of pam_tally2 for Touch login and screenunlock
This bug was fixed in the package lightdm - 1.11.5-0ubuntu1 --- lightdm (1.11.5-0ubuntu1) utopic; urgency=medium * New upstream release: - Make PAM services configurable (LP: #1348251) * debian/guest-account: * debian/lightdm.install: * debian/rules: * debian/patches/05_translate_debian_files.patch: - Make the real name of a guest account translatable (LP: #1177713) -- Robert Ancell robert.anc...@canonical.com Mon, 28 Jul 2014 13:40:46 +1200 ** Changed in: lightdm (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1348251 Title: please make use of pam_tally2 for Touch login and screenunlock Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “ubuntu-touch-session” package in Ubuntu: New Bug description: Ubuntu Touch will soon have/now has the ability to set a PIN/password for the user. If the password is set, we should provide some protection against brute force password guessing since many users will choose to use PINs rather than proper passwords. This is required for devices for RTM, but not for the traditional Ubuntu desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1348251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1177713] Re: Unity: Name of Guest account not internationalized
This bug was fixed in the package lightdm - 1.11.5-0ubuntu1 --- lightdm (1.11.5-0ubuntu1) utopic; urgency=medium * New upstream release: - Make PAM services configurable (LP: #1348251) * debian/guest-account: * debian/lightdm.install: * debian/rules: * debian/patches/05_translate_debian_files.patch: - Make the real name of a guest account translatable (LP: #1177713) -- Robert Ancell robert.anc...@canonical.com Mon, 28 Jul 2014 13:40:46 +1200 ** Changed in: lightdm (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1177713 Title: Unity: Name of Guest account not internationalized Status in Ubuntu Translations: Triaged Status in Unity: Confirmed Status in “lightdm” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: Login on a guest session Click on logout from guest session Result: There is a dialog, asking whether you're sure to log out. Auf Wiedersehen, Guest. Sind Sie sicher, dass sie alle Programme schließen und sich von Ihrem Konto abmelden möchten? In this string Guest is not translated to Gast. Using Ubuntu 13.04 Locale: German, Germany To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1177713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1236258] Re: using apt-get gives E: Method gave invalid 200 URI Start message for every repository
** Changed in: aptitude (Ubuntu) Status: Confirmed = Invalid -- 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/1236258 Title: using apt-get gives E: Method gave invalid 200 URI Start message for every repository Status in “apt” package in Ubuntu: Confirmed Status in “aptitude” package in Ubuntu: Invalid Bug description: Since I updated to saucy I always get: E: Method gave invalid 200 URI Start message when using apt-get or aptitude. I've disabled all sources except for the main archive, but I still get this message. I also get it for all mirrors I tried (US, NL). Full message: $ sudo aptitude update Ign http://archive.ubuntu.com saucy InRelease Hit http://archive.ubuntu.com saucy Release.gpg Hit http://archive.ubuntu.com saucy Release Hit http://archive.ubuntu.com saucy/main amd64 Packages Get: 1 http://archive.ubuntu.com saucy/main i386 Packages [1,256 kB] Get: 2 http://archive.ubuntu.com saucy/main Translation-en [712 kB] Fetched 2 B in 0s (13 B/s) E: Method gave invalid 200 URI Start message ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apt 0.9.9.1~ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 11:51:30 2013 InstallationDate: Installed on 2012-09-27 (374 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120612) MarkForUpload: True SourcePackage: apt UpgradeStatus: Upgraded to saucy on 2013-10-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1236258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1208001] Re: [G31M-S2L, Realtek ALC883, Green Line Out, Rear] No sound at all
Default sink name: alsa_output.pci-_01_00.1.hdmi-stereo-extra1 Default source name: alsa_input.pci-_00_1b.0.analog-stereo pulseaudio change the default sink to hdmi and the digital device instead of analog is the active profile you have to find out why it is auto selected or your selection in sound preference are not saved and restore after boot active profile: output:iec958-stereo+input:analog-stereo sinks: -- 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/1208001 Title: [G31M-S2L, Realtek ALC883, Green Line Out, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: i dont hear any sound ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16 Uname: Linux 3.5.0-37-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25. ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: santhosh 1488 F pulseaudio /dev/snd/controlC0: santhosh 1488 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xe410 irq 44' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,1458c603,0012' Controls : 45 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xe200 irq 17' Mixer name : 'Nvidia GPU 0b HDMI/DP' Components : 'HDA:10de000b,10de0101,00100200' Controls : 24 Simple ctrls : 4 Date: Sat Aug 3 19:37:03 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en TERM=xterm PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: 1488 1488 santhosh F pulseaudio /dev/snd/controlC0: santhosh F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [G31M-S2L, Realtek ALC883, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7C dmi.board.name: G31M-S2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7C:bd07/30/2008:svnGigabyteTechnologyCo.,Ltd.:pnG31M-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-S2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-S2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1208001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1310690] Re: Lock screen password field does not capture key press - password is disclosed in background application
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete = Expired -- 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/1310690 Title: Lock screen password field does not capture key press - password is disclosed in background application Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 times already) that the password field doesn't capture the key presses sometimes. Key presses are not registered by the field and it looks like it is frozen (except by the cursor blinking). What I had to do when this happened was to wait until the tentative expires (screen goes blank) and then try again - then it worked. However the application running in the foregroung (or background, if you consider the lockscreen is on top) received the key presses, i.e, my whole password - you can imagine the implications if it was a chat window. I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1310690/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313102] Re: internal compiler error with std::array designated initialization
** Branch linked: lp:debian/gnat-4.9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1313102
Title:
internal compiler error with std::array designated initialization
Status in The GNU Compiler Collection:
New
Status in “gcc-4.8” package in Ubuntu:
Fix Released
Status in “gcc-4.9” package in Ubuntu:
Fix Released
Status in “gccgo-4.9” package in Ubuntu:
Invalid
Status in “gcc-4.8” source package in Trusty:
New
Status in “gcc-4.9” source package in Trusty:
Invalid
Status in “gccgo-4.9” source package in Trusty:
New
Bug description:
The following code fails to compile with g++-4.8:
#include array
const int i = 0;
std::arrayint, 1 bar = {
[i] = 0
};
I have since learned that designated initialization is not supported
in (GNU) C++. In that case I would have expected a syntax error.
This is the compilation command and its output:
$ g++-4.8 -Wall -std=gnu++11 main.cpp
main.cpp:5:1: internal compiler error: in lookup_field_1, at
cp/search.c:384
};
^
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions.
Preprocessed source stored into /tmp/ccUsV9BC.out file, please attach this
to your bugreport.
The preprocessed source file is attached. g++-4.8 --version reports
g++-4.8 (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1. I installed this package
using the instructions given in this answer:
http://askubuntu.com/a/271561. Ubuntu release and package version
are:
$ lsb_release -rd
Description:Ubuntu 12.04.4 LTS
Release:12.04
$ apt-cache policy g++-4.8
g++-4.8:
Installed: 4.8.1-2ubuntu1~12.04
Candidate: 4.8.1-2ubuntu1~12.04
Version table:
*** 4.8.1-2ubuntu1~12.04 0
500 http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu/
precise/main i386 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1313102/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349240] [NEW] Opening new tab causes browser to unmaximize on Ubuntu Desktop (Unity 7)
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center webbrowser-app: Installed: 0.23+14.10.20140724.1-0ubuntu1 Candidate: 0.23+14.10.20140724.1-0ubuntu1 Version table: *** 0.23+14.10.20140724.1-0ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen a) Maximize webbrowser b) HUD New Tab c) webbrowser stays Maximized 4) What happened instead a) Maximize webbrowser b) HUD New Tab c) webbrowser shrinks to smaller window ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1349240 Title: Opening new tab causes browser to unmaximize on Ubuntu Desktop (Unity 7) Status in “webbrowser-app” package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center webbrowser-app: Installed: 0.23+14.10.20140724.1-0ubuntu1 Candidate: 0.23+14.10.20140724.1-0ubuntu1 Version table: *** 0.23+14.10.20140724.1-0ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen a) Maximize webbrowser b) HUD New Tab c) webbrowser stays Maximized 4) What happened instead a) Maximize webbrowser b) HUD New Tab c) webbrowser shrinks to smaller window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1349240/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348668] Re: Unity lockscreen lets applications capture keyboard input
That affects different Google Chrome inputs. Address bar, Google search bar, Google Keep inputs and so on. It's not limited to a special extension. (I use a Zenbook Prime UX31A with Ubuntu 14.04 running.) Maybe other programs are affected too, but I don't think so. Can't reproduce it with Gedit for example. -- 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/1348668 Title: Unity lockscreen lets applications capture keyboard input Status in “unity” package in Ubuntu: New Bug description: I noticed that with the Vimium extension activated in Google Chrome, I cannot unlock Unity's lockscreen because keyboard input is hijacked by Vimium. The lockscreen really should not let this happen, and it can even be considered a potential security vulnerability as it might allow applications to capture a user's password. I have noticed this before as well when using another application, though I can't remember which one it was at the moment. The workaround is to use the mouse to choose the Switch user-option, but this is really not obvious to anyone who might encounter this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1348668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323279] Re: Fringe colors around letters in non-focused window titles
I don't believe that is a driver bug. To me it looks like a blur has been applied to the unfocused titlebar. Unity? ** Changed in: xserver-xorg-video-intel (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/1323279 Title: Fringe colors around letters in non-focused window titles Status in “xorg” package in Ubuntu: New Status in “xserver-xorg-video-intel” package in Ubuntu: Invalid Bug description: The letters in the titles of the non-focused windows have hints of blue and red. It looks like sub-pixel antialiasing done wrong. This strange effect can also be seen in screenshots (see the attached file). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.15.0-031500rc5-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: Mon May 26 14:21:01 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.15.0-031500rc5-generic, x86_64: installed EcryptfsInUse: Yes 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: Lenovo Device [17aa:3097] InstallationDate: Installed on 2014-05-15 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: LENOVO 10A7000LGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-031500rc5-generic root=UUID=f2abe8d7-641e-4e8a-917e-b909f8d55171 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKT72AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKT72AUS:bd01/26/2014:svnLENOVO:pn10A7000LGE:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvr0B98401PRO:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 10A7000LGE dmi.product.version: ThinkCentre M93p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.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 May 19 18:17:31 2014 xserver.configfile: default xserver.errors: PreInit returned 8 for Logitech Inc. Logitech USB Headset H340 PreInit returned 8 for Logitech Inc. Logitech USB Headset H340 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41083 vendor DEL xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1323279/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329939] Re: Service ssh stop/start/restart hangs
Hello again, I forgot to mention that I have MANY defuncts after one day: ps -ef | grep sshd root 696 11633 0 Jul26 ?00:00:00 [sshd] defunct root 698 11633 0 Jul26 ?00:00:00 [sshd] defunct root 700 11633 0 Jul26 ?00:00:00 [sshd] defunct root 748 11633 0 Jul26 ?00:00:00 [sshd] defunct root 750 11633 0 Jul26 ?00:00:00 [sshd] defunct root 752 11633 0 Jul26 ?00:00:00 [sshd] defunct root 754 11633 0 Jul26 ?00:00:00 [sshd] defunct root 1648 11633 0 05:44 ?00:00:00 [sshd] defunct root 4106 11633 0 Jul26 ?00:00:00 [sshd] defunct root 4108 11633 0 Jul26 ?00:00:00 [sshd] defunct root 4156 11633 0 Jul26 ?00:00:00 [sshd] defunct root 4158 11633 0 Jul26 ?00:00:00 [sshd] defunct root 4278 11633 0 Jul26 ?00:00:00 [sshd] defunct root 4280 11633 0 Jul26 ?00:00:00 [sshd] defunct root 4282 11633 0 Jul26 ?00:00:00 [sshd] defunct root 4284 11633 0 Jul26 ?00:00:00 [sshd] defunct root 7265 1 0 Jul26 ?00:00:00 [sshd] defunct ajurak7392 1 0 Jul26 ?00:00:02 [sshd] defunct root 7638 1 0 Jul26 ?00:00:00 [sshd] defunct ajurak7686 1 0 Jul26 ?00:00:00 [sshd] defunct root 11102 11633 0 07:01 ?00:00:00 [sshd] defunct sshd 11103 1 0 07:01 ?00:00:00 [sshd] defunct root 11104 11633 0 07:01 ?00:00:00 [sshd] defunct sshd 11105 1 0 07:01 ?00:00:00 [sshd] defunct root 11165 11633 0 07:01 ?00:00:00 [sshd] defunct sshd 11166 1 0 07:01 ?00:00:00 [sshd] defunct root 11229 11633 0 07:02 ?00:00:00 [sshd] defunct sshd 11230 1 0 07:02 ?00:00:00 [sshd] defunct root 11231 11633 0 07:02 ?00:00:00 [sshd] defunct sshd 11232 1 0 07:02 ?00:00:00 [sshd] defunct root 11355 11633 0 07:03 ?00:00:00 [sshd] defunct sshd 11356 1 0 07:03 ?00:00:00 [sshd] defunct root 11357 11633 0 07:03 ?00:00:00 [sshd] defunct sshd 11358 1 0 07:03 ?00:00:00 [sshd] defunct root 11597 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11599 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11633 1 0 Jul26 ?00:00:00 /usr/sbin/sshd -D root 11653 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11663 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11724 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11726 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11728 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11822 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11824 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11828 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11830 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11951 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11952 11633 0 07:08 ?00:00:00 [sshd] defunct sshd 11953 1 0 07:08 ?00:00:00 [sshd] defunct root 11954 11633 0 07:08 ?00:00:00 [sshd] defunct sshd 11955 1 0 07:08 ?00:00:00 [sshd] defunct root 11983 11633 0 Jul26 ?00:00:00 [sshd] defunct root 11985 11633 0 Jul26 ?00:00:00 [sshd] defunct root 12004 11633 0 07:08 ?00:00:00 [sshd] defunct sshd 12005 1 0 07:08 ?00:00:00 [sshd] defunct root 12033 11633 0 Jul26 ?00:00:00 [sshd] defunct root 12081 11633 0 Jul26 ?00:00:00 [sshd] defunct root 12083 11633 0 Jul26 ?00:00:00 [sshd] defunct root 12085 11633 0 Jul26 ?00:00:00 [sshd] defunct root 12100 11633 0 07:09 ?00:00:00 [sshd] defunct sshd 12101 1 0 07:09 ?00:00:00 [sshd] defunct root 12102 11633 0 07:09 ?00:00:00 [sshd] defunct sshd 12103 1 0 07:09 ?00:00:00 [sshd] defunct root 12104 11633 0 07:09 ?00:00:00 [sshd] defunct sshd 12105 1 0 07:09 ?00:00:00 [sshd] defunct root 12106 11633 0 07:09 ?00:00:00 [sshd] defunct sshd 12107 1 0 07:09 ?00:00:00 [sshd] defunct root 12108 11633 0 07:09 ?00:00:00 [sshd] defunct sshd 12109 1 0 07:09 ?00:00:00 [sshd] defunct root 12110 11633 0 07:09 ?00:00:00 [sshd] defunct sshd 12111 1 0 07:09 ?00:00:00 [sshd] defunct root 12112 11633 0 07:09 ?00:00:00 [sshd] defunct sshd 12113 1 0 07:09 ?00:00:00 [sshd] defunct root 12114 11633 0 07:09 ?00:00:00 [sshd] defunct sshd 12115 1 0 07:09 ?00:00:00 [sshd] defunct root 12125 11633 0 Jul26 ?00:00:00 [sshd] defunct root 12148 11633 0 Jul26 ?00:00:00 [sshd] defunct root 12196 11633 0 07:10 ?00:00:00
[Touch-packages] [Bug 465916] Re: CUPS DNS-SD (Bonjour/mDNS/Zeroconf/Avahi) not broadcasting
This bug appears to be back on Trusty, with a Samsung laser printer
attached to my router.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/465916
Title:
CUPS DNS-SD (Bonjour/mDNS/Zeroconf/Avahi) not broadcasting
Status in Avahi:
New
Status in “cups” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: cups
I've enabled advertising of local printers in a recent upgrade to
Karmic. The config file has these salient lines:
Browsing On
BrowseOrder allow,deny
BrowseAllow all
BrowseRemoteProtocols cups
BrowseAddress @LOCAL
BrowseLocalProtocols cups dnssd
But CUPS still doesn't advertise using DNS-SD. (I can't find the
printers with a Mac OS X v10.6 client, and I also checked by running
avahi-browse locally.) I turned the log level to debug2 and didn't
find any indication that DNS-SD was being used. (In particular, I
expected dnssdRegisterPrinter to be logged, as reflected by line
2666 of dirsvc.c in the CUPS source.) Suspiciously, I noticed this
line in the log file:
d [30/Oct/2009:14:35:13 -0700] [CGI] Starting {HAVE_DNSSD? at 2802,
result=0...
d [30/Oct/2009:14:35:13 -0700] [CGI] Skip first part...
I don't exactly know what's going on here, but is it possible that
CUPS was for some reason compiled with the HAVE_DNSSD flag off?
Further evidence: If I click Advanced on the Administration page,
the protocols under Share printers connected to this system are
CUPS, LDAP, and SLP. No DNS-SD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/avahi/+bug/465916/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 465916] Re: CUPS DNS-SD (Bonjour/mDNS/Zeroconf/Avahi) not broadcasting
PS The standard Add Printer dialog does not find the Samsung networked
pnte.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/465916
Title:
CUPS DNS-SD (Bonjour/mDNS/Zeroconf/Avahi) not broadcasting
Status in Avahi:
New
Status in “cups” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: cups
I've enabled advertising of local printers in a recent upgrade to
Karmic. The config file has these salient lines:
Browsing On
BrowseOrder allow,deny
BrowseAllow all
BrowseRemoteProtocols cups
BrowseAddress @LOCAL
BrowseLocalProtocols cups dnssd
But CUPS still doesn't advertise using DNS-SD. (I can't find the
printers with a Mac OS X v10.6 client, and I also checked by running
avahi-browse locally.) I turned the log level to debug2 and didn't
find any indication that DNS-SD was being used. (In particular, I
expected dnssdRegisterPrinter to be logged, as reflected by line
2666 of dirsvc.c in the CUPS source.) Suspiciously, I noticed this
line in the log file:
d [30/Oct/2009:14:35:13 -0700] [CGI] Starting {HAVE_DNSSD? at 2802,
result=0...
d [30/Oct/2009:14:35:13 -0700] [CGI] Skip first part...
I don't exactly know what's going on here, but is it possible that
CUPS was for some reason compiled with the HAVE_DNSSD flag off?
Further evidence: If I click Advanced on the Administration page,
the protocols under Share printers connected to this system are
CUPS, LDAP, and SLP. No DNS-SD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/avahi/+bug/465916/+subscriptions
--
Mailing list: https://launchpad.net/~touch-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
It's been happening on my laptop since 13.04, and the reason was and still is (on 14.04) opening Nautilus on a Folder that contains either Photos and/or Videos, and once the Thumbnails are shown, then my i7 CPU feels like it's burning, really burning and the fan wants to fly, the hud-service goes crazy consuming both the CPU resources and the memory, which goes up to 1.7GB in no time. Surely it's a memory leak sort of thing. -- 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(QSharedPointerhud::service::Window) () #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/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31
[Touch-packages] [Bug 1329468] Re: [W230SS, VIA1802] no sound from headphones
*** This bug is a duplicate of bug 1313904 *** https://bugs.launchpad.net/bugs/1313904 ** This bug has been marked a duplicate of bug 1313904 [W230SS, VIA VT1802, Green Headphone Out, Front] No sound after fresh boot -- 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/1329468 Title: [W230SS, VIA1802] no sound from headphones Status in “alsa-driver” package in Ubuntu: New Bug description: ubuntu 14.04 live usb, on my new laptop (also happens after installation). what happened When the headphones are unplugged I hear sounds from the internal speakers(correct). When the headphones are plugged in I hear no sounds. (bug). What I expected When internal the headphones are plugged in, the internal speakers are muted, and I can hear sounds from the headphones. Steps to reproduce 0. boot ubuntu 14.04 LTR from usb 1. play song 2. plug in headphones into headphone jack 3. unplug headphones 4. write bug report codecs are installed https://wiki.ubuntu.com/Audio/HDAGeneric command grep Codec: /proc/asound/card*/codec* output /proc/asound/card0/codec#0:Codec: Intel Haswell HDMI /proc/asound/card1/codec#0:Codec: VIA VT1802 Laptop model xmg p304 http://www.mysn.eu/se/xmg-p304 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 2312 F pulseaudio /dev/snd/controlC1: ubuntu 2312 F pulseaudio CasperVersion: 1.340 CurrentDesktop: Unity Date: Thu Jun 12 18:32:07 2014 LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [W230SS, VIA VT1802, Green Headphone Out, Front] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/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:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1329468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346766] Re: Chinese in Ubuntu Touch should use Heiti style sans serif font
** Description changed: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy-microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. fonts-droid (DroidSansFallbackFull.ttf, original): - Pros: - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. -Cons: - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. As an additional alternative, just a few days ago, Google released the Noto Sans CJK fonts [2][3]: fonts-noto (Noto Sans CJK fonts): - Pros: - - It takes care of different writing standard of Traditional and Simplified Chinese + - It takes care of different writing standards of Traditional Chinese, Simplified Chinese, Japanese and Korean, which makes everyone happy (see slide 13-14 of [3]) - It covers Japanese and Korean as well - Cons: - Needs to be tested - Bigger size than the other alternatives as a result of catering for both Traditional and Simplified Chinese - Not yet packaged [4] [1] https://en.wikipedia.org/wiki/CJK_Unified_Ideographs_Extension_A [2] http://googledevelopers.blogspot.de/2014/07/noto-cjk-font-that-is-complete.html [3] https://docs.google.com/presentation/d/1xIBCsqwrSxowmLQS7kJm9gM58-FmOIYlZWoRlgqtqE4/edit#slide=id.g36327fada_643 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754926 -- 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/1346766 Title: Chinese in Ubuntu Touch should use Heiti style sans serif font Status in “ubuntu-touch-meta” package in Ubuntu: Confirmed Bug description: Ubuntu Touch uses Kaiti style font as the main UI font for displaying Chinese, which is not optimal as nowadays operating systems all use Heiti style font for the UI, we should really change it asap. Currently there are two choices on Ubuntu, fonts-droid and wqy- microhei. Below I will list out the pros and cons. wqy-microhei (DroidSansFallbackFull.ttf, modified): - Pros: - The advantage of wqy-microhei being its wider codepoint coverage, for example it also contains Japanese Kanas and Korean Hanguls in one font. The downside is it may be of lower quality than the original DroidSansFallbackFull.ttf due to its lack of maintenance in recent years. - Cons: - I am not too much in favour of using wqy-microhei, the reason being that it is basically a font that based on the Droid font (DroidSansFallbackFull.ttf to be exact). - Upstream has not updated wqy-microhei for long time, so it lacks any new updates from the Droid font, although it may not be obvious to users. - Another possible disadvantage of wqy-microhei is it includes more latin characters, which may result to inconsistent glyphs being used. fonts-droid (DroidSansFallbackFull.ttf, original): - Pros: - The advantage is it has coverage of CJK ext. A [1], which wqy-microhei does not provide. -Cons: - On the other hand, wqy-microhei has added some glyphs that the droid font does not provide, I don't have the exact number of that but I believe it's just a small number. - The disadvantage is it does not include Korean Hangul, which can be remedied with another Korean font, and it's not our current concern anyway. As an additional alternative, just a few days ago, Google released the Noto Sans CJK fonts [2][3]: fonts-noto (Noto Sans CJK fonts): - Pros: - It takes care of different writing standards of Traditional Chinese, Simplified Chinese, Japanese and Korean, which makes everyone happy (see slide 13-14 of [3]) - It covers Japanese
[Touch-packages] [Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Solution #32 , appending session required pam_loginuid.so session required pam_systemd.so to /etc/pam.d/lxdm made everything work. Thanks -- 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/1240336 Title: Not authorized to perform operation / Unable to determine the session we are in: No session for pid Status in “gdm” package in Ubuntu: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lxdm” package in Ubuntu: Confirmed Status in “policykit-desktop-privileges” package in Ubuntu: Confirmed Bug description: After a new install of 64 bit Ubuntu 13.10 on my second partition, I used dpkg to reinstall all the same packages I had on my 32 bit 13.04 partition. I copied all my home directory files over and updated all the packages. I now find that I don't have permissions to change the network settings; I can't mount my other hard drive or any USB stick using nautilus, or (udisks without using sudo)' I can't run synaptic by clicking on the GUI (I have to go to a terminal and sudo synaptic); etc. I can't find any documentation on the configuration of policykit-desktop-privileges, so I'm filing this bug. For me it appears to be totally broken. Maybe someone can help me out. Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 746383] Re: fontconfig confuses bold and medium weights
** Changed in: pango Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/746383 Title: fontconfig confuses bold and medium weights Status in Fontconfig - Font Configuration Library: Confirmed Status in Pango - Layout and Text Rendering LIbrary: Fix Released Status in “fontconfig” package in Ubuntu: Triaged Status in “pango” package in Ubuntu: Triaged Bug description: Attempts to set Ubuntu Bold in the Appearance settings fall back to Ubuntu Medium. In fact, in the font selection screen there seems to be no difference between bold and medium. Curiously enough, Bug #746382 sort of proves that Ubuntu Bold *is* installed and accessible. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ttf-ubuntu-font-family 0.71.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Thu Mar 31 08:33:44 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110325) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-font-family-sources UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/746383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1014074] Re: HDMI on Gigabyte HD7770 OC 1GB not supported in Precise Pangolin
Ubuntu 14.04 Trusty Tahr contains a 3.13-based kernel. This kernel includes HDMI audio support for Radeon HD7xxx hardware. Also, the radeon.audio=1 kernel boot option is no longer necessary with this kernel. Instead, HDMI audio on ATI/AMD Radeon cards can be enabled and disabled on the fly by typing the following in a terminal window: xrandr --output HDMI-0 --set audio on or xrandr --output HDMI-0 --set audio off If your HDMI port is numbered differently (type xrandr to check) - you might need to change HDMI-0 in the above command to HDMI-1 or HDMI-2. -- 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/1014074 Title: HDMI on Gigabyte HD7770 OC 1GB not supported in Precise Pangolin Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Unless I blacklist snd_had_codec_hdmi, the sound subsystem refuses to start and I get no sound at all, not even from the motherboard's ALC892. This is the ouput from alsa-script.sh with snd_hda_codec_hdmi: !! !!ALSA Information Script v 0.4.61 !! !!Script ran on: Fri Jun 15 22:12:19 UTC 2012 !!Linux Distribution !!-- Ubuntu 12.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION=Ubuntu 12.04 LTS !!DMI Information !!--- Manufacturer: To be filled by O.E.M. Product Name: To be filled by O.E.M. Product Version: To be filled by O.E.M. Firmware Version: 1102 !!Kernel Information !!-- Kernel release:3.2.0-25-generic-pae Operating System: GNU/Linux Architecture: i686 Processor: athlon SMP Enabled: Yes !!ALSA Version !! Driver version: 1.0.24 Library version:1.0.25 Utilities version: 1.0.25 !!Loaded ALSA modules !!--- snd_hda_intel snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfeb0 irq 16 1 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xfea6 irq 87 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) (rev 40) 01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Device aab0 !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:14.2 0403: 1002:4383 (rev 40) Subsystem: 1043:8410 -- 01:00.1 0403: 1002:aab0 Subsystem: 1458:aab0 !!Modprobe options (Sound related) !! snd-atiixp-modem: index=-2 snd-intel8x0m: index=-2 snd-via82xx-modem: index=-2 snd-usb-audio: index=-2 snd-usb-caiaq: index=-2 snd-usb-ua101: index=-2 snd-usb-us122l: index=-2 snd-usb-usx2y: index=-2 snd-cmipci: mpu_port=0x330 fm_port=0x388 snd-pcsp: index=-2 snd-usb-audio: index=-2 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : Y bdl_pos_adj : 32,32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 model : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) patch : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) position_fix : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 power_save : 0 power_save_controller : Y probe_mask : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 probe_only : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 single_cmd : N
[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop
** Branch linked: lp:~hennekn/ubuntu/trusty/ibus/bug-1240198 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: Wrong keyboard layout active after booting into desktop Status in “ibus” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=de XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 897548] Re: ibus-daemon crashed on startup with SIGABRT in g_assertion_message()
** 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/897548 Title: ibus-daemon crashed on startup with SIGABRT in g_assertion_message() Status in “ibus” package in Ubuntu: New Bug description: This crash occurs sometimes (without any obvious pattern) on KDE login when ibus-daemon is started. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: ibus 1.3.99.20110419-1ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic-pae 3.0.6 Uname: Linux 3.0.0-13-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu4 Architecture: i386 CrashCounter: 1 Date: Tue Nov 29 10:10:40 2011 ExecutablePath: /usr/bin/ibus-daemon ProcCmdline: /usr/bin/ibus-daemon -Rr --xim Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message (domain=0xb7427910 IBUS, file=0xb742c4cc ibusbus.c, line=242, func=0xb742c831 _connection_closed_cb, message=optimized out) at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1425 g_assertion_message_expr (domain=0xb7427910 IBUS, file=0xb742c4cc ibusbus.c, line=242, func=0xb742c831 _connection_closed_cb, expr=0xb742bf18 bus-priv-connection == connection) at /build/buildd/glib2.0-2.30.0/./glib/gtestutils.c:1436 ?? () from /usr/lib/libibus-1.0.so.0 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to oneiric on 2011-10-14 (45 days ago) UserGroups: adm admin audio cdrom debian-transmission dialout fax floppy lpadmin plugdev sambashare scanner syslog vboxusers video wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/897548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 407585] Re: use system keyboard layout setting by default
*** This bug is a duplicate of bug 1240198 *** https://bugs.launchpad.net/bugs/1240198 ** This bug has been marked a duplicate of bug 1240198 Wrong keyboard layout active after booting into desktop -- 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/407585 Title: use system keyboard layout setting by default Status in “ibus” package in Ubuntu: Triaged Bug description: Binary package hint: ibus the current default for ibus preferences - advanced - keyboard layout - use system keyboard layout is off. I think the sane default in this case is on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/407585/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 998751] Re: ibus prevents minecraft to get keyboard input
Don't think this is an IBus bug as it works only when ibus isn't handling XIM, which is not possible for people using input method day to day. I believe this should be reported to Minecraft instead. ** Changed in: ibus (Ubuntu) Status: Triaged = Invalid -- 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/998751 Title: ibus prevents minecraft to get keyboard input Status in IBus: Unknown Status in “ibus” package in Ubuntu: Invalid Bug description: when ibus is running, some apps don't get keyboard input. for example, minecraft is one such application when the ibus process is killed, minecraft gets keyboard input fine I've tried this with three different JDKs, with the same result: * OpenJDK 6 * OpenJDK 7 * Oracle JDK 7 I would expect minecraft to get keyboard input when ibus is running as well ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ibus 1.4.1-3ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sun May 13 15:29:09 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: ibus UpgradeStatus: Upgraded to precise on 2012-05-09 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/998751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1236280] Re: [right edge] Dash should appear in the right edge interaction as just another app
** Branch linked: lp:~mzanetti/unity8/dash-as-app -- 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/1236280 Title: [right edge] Dash should appear in the right edge interaction as just another app Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: Dash should appear in the right edge interaction as just another app. Use Case: 1. User is in the Dash Music Scope. They select an album to play. 2. Phone switches the user to the Music App and the album starts to play 3. User performs a right edge gesture to switch back to the previous app Current incorrect behaviour: 4. Phone switches the User to the app they were using before they entered the Dash (they are not switched to the Dash) Correct desired behaviour: 4. Phone switches the User to the Dash, because if we treat the Dash as an app, the Dash was the last app the user used before they switched to the Music App. Notes: - This change should be made to both the current right edge switcher, and the new alt-tab style 3d right edge switcher - When the user returns to the Dash, they should return to exactly the same state they left the Dash from e.g. Focused Scope, scroll position and preview open/closed should persist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1236280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1344427] Re: [Vaio VGN-A417S] XUbuntu 14.04 NO audio from internal Device
you have to fix the pin by hda jack retask try hda jack sense to find the nodes of HP and Mic jack by plug and unplug remove redundant pin e.g. CD if the internal speaker and Mic is not correct, you have to retask the remaining nodes one at a time -- 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/1344427 Title: [Vaio VGN-A417S] XUbuntu 14.04 NO audio from internal Device Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: hello, Clean install of Xubuntu 14.04. NO audio output. In Input TAB i have Internal stereo analogic audio (in italian Audio Interno Stereo Analogic) but in port: i have 3 voices 1 Anterior mic (unplugged) 1 Posterior mic (plugged in) 1 Line IN (plugged) but the choise change in automatic very fast whitout i click anyting. http://www.alsa- project.org/db/?f=4fccdc82d94f8c23f1bab24aed689ba3ff4c0b15 Best Regards --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm1152 F pulseaudio ty 1579 F pulseaudio lightdm 10519 F pulseaudio DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-18 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Tags: trusty Uname: Linux 3.13.0-24-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/14/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0080F2 dmi.chassis.asset.tag: 8T1Me91a5428e8e9921f dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0080F2:bd03/14/2005:svnSonyCorporation:pnVGN-A417S:pvrC0007XEJ:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-A417S dmi.product.version: C0007XEJ dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1344427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333261] Re: Left-edge long-swipe dash fade-in is not smooth
** Branch linked: lp:~mzanetti/unity8/dash-as-app -- 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/1333261 Title: Left-edge long-swipe dash fade-in is not smooth Status in The Unity 8 shell: Triaged Status in “unity8” package in Ubuntu: Confirmed Bug description: * launch an app * long-swipe from the left → see that the dash doesn't fade-in smoothly but jumps ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.89+14.10.20140619.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 23 15:36:06 2014 SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1333261/+subscriptions -- Mailing list: https://launchpad.net/~touch-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 fresh boot
Hi Urund, You are correct, after more investigation I came to same conclusion. It is described at kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=75151 I have posted alsa logs there. And about InitHeadphone: this is cool, solution for windows is found, and maybe someone could make research in hp.dll to prepare solution for linux... -- 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 fresh boot Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: When I boot Windows and then reboot into Ubuntu the sound is ok. But when I am booting after turning laptop on there are no sound in headphone jack. Mic jack works fine. Also heaphone stop working after putting laptop to sleep. 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 1283032] Re: PageHeader doesn't render correctly
** Changed in: unity8 Status: New = Fix Released ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1283032 Title: PageHeader doesn't render correctly Status in The Unity 8 shell: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: When switching dash page via the scopes scope (by clicking for example on the apps scope), the header doesn't often render correctly, and a scroll or a tap is required for it to render correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1283032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 711775] Re: subtitles encoding is not shown properly in vlc
** Changed in: ibus (Ubuntu) Status: Confirmed = New -- 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/711775 Title: subtitles encoding is not shown properly in vlc Status in “vlc” package in Ubuntu: New Bug description: Binary package hint: ibus When I run vlc to see a movie with Windows-1251 subtitles, the vlc shows following error: [0x7f709c05dd50] subsdec decoder error: failed to convert subtitle encoding. Try manually setting a character-encoding before you open the file. Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon Warning: call to rand() and the text of the subtitles is shown as question marks. If I remove the ibus and all it's libraries, the VLC works properly. My guess is that the ibus did not start on boot, thus I am filing the bug against ibus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/711775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 711775] Re: subtitles encoding is not shown properly in vlc
** Package changed: ibus (Ubuntu) = vlc (Ubuntu) -- 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/711775 Title: subtitles encoding is not shown properly in vlc Status in “vlc” package in Ubuntu: New Bug description: Binary package hint: ibus When I run vlc to see a movie with Windows-1251 subtitles, the vlc shows following error: [0x7f709c05dd50] subsdec decoder error: failed to convert subtitle encoding. Try manually setting a character-encoding before you open the file. Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon Warning: call to rand() and the text of the subtitles is shown as question marks. If I remove the ibus and all it's libraries, the VLC works properly. My guess is that the ibus did not start on boot, thus I am filing the bug against ibus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/711775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 522814] Re: ibus does not install itself as an option for the all_ALL quasi-locale
These stuff are handled in im-config nowadays. ** Package changed: ibus (Ubuntu) = im-config (Ubuntu) ** Changed in: im-config (Ubuntu) Status: Confirmed = New -- 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/522814 Title: ibus does not install itself as an option for the all_ALL quasi-locale Status in “im-config” package in Ubuntu: New Bug description: Binary package hint: ibus Upon installation, ibus installs itself as a choice for several locales (xinput-lang_LANG alternatives), including ja_JP and ko_KR. This allows for use of the im-switch tool to change what input method to use for that locale. It does not install itself as an option for the all_ALL quasi-locale, or more specifically, the xinput-all_ALL alternative. This makes it impossible to use im-switch to set my system-wide default to ibus. I run Kubuntu 10.04 with an English language setting and a Swedish locale. This behavior is present in Karmic as well. $ sudo im-switch -c No system wide default defined just for locale en_US . Use all_ALL quasi-locale and set IM. System wide default for all_ALL locale is marked with [+]. There are 7 choices for the alternative xinput-all_ALL (providing /etc/X11/xinit/xinput.d/all_ALL). SelectionPathPriority Status * 0/etc/X11/xinit/xinput.d/default 10auto mode 1/etc/X11/xinit/xinput.d/default 10manual mode 2/etc/X11/xinit/xinput.d/default-xim 0 manual mode 3/etc/X11/xinit/xinput.d/none 0 manual mode 4/etc/X11/xinit/xinput.d/uim 0 manual mode 5/etc/X11/xinit/xinput.d/uim-systray 0 manual mode 6/etc/X11/xinit/xinput.d/uim-toolbar 0 manual mode 7/etc/X11/xinit/xinput.d/uim-toolbar-qt 0 manual mode Press enter to keep the current choice[*], or type selection number: As workarounds go, it is possible to modify the alternative configuration file (/var/lib/dpkg/alternatives/xinput-all_ALL) to include ibus, or to manually repoint the symlink at /etc/alternatives /xinput-all_ALL. I can also overwrite /etc/X11/xinit/xinput.d/default with the contents of the ibus file in the same directory. Looking at the source, all_ALL is commented out at debian/ibus.postinst:12. Excerpt; case $1 in configure) #ua_inst all_ALL ibus 0 ua_inst ja_JP ibus 60 ua_inst ko_KR ibus 60 [...] Unsure of the rationale of why it would be disabled that way. Both UIM and SCIM install themselves as choices to all_ALL, so installation of those methods is very easy. ProblemType: Bug Architecture: i386 Date: Tue Feb 16 20:28:01 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Kubuntu 10.04 Lucid Lynx - Alpha i386 (20100201) Package: ibus 1.2.0.20091215-1ubuntu1 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-12.17-generic SourcePackage: ibus Uname: Linux 2.6.32-12-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/522814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299759] Re: ibus daemon cpu use flares up briefly when editing in Gedit
Setting the input method to none does not work here. Same 19% CPU activity of ibus-daemon, fann running high. However, task-switching to another application than gedit stops the ibus usage temporarily. -- 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/1299759 Title: ibus daemon cpu use flares up briefly when editing in Gedit Status in “ibus” package in Ubuntu: Confirmed Bug description: When resuming an edit in Gedit, the ibus daemon flares up, abusing the CPU for a short while. This happens every time lately. All that's needed is to switch windows back to Gedit and resume editing. Then the CPU usage spikes for a moment before going back down. I would expect that the correct behavir is for the CPU usage to stay low, no matter the activity in Gedit. top has the following, sometimes even higher use, but it's very hard to catch since it happens for only a moment: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2730 user 20 0 373672 23440 1740 R 172,6 0,6 45:11.21 ibus-daemon 2756 user 20 0 285672 3660 2604 S 105,9 0,1 26:31.45 ibus-x11 2525 root 20 0 358760 118124 21216 S 87,6 3,0 197:29.28 Xorg 11441 user 20 0 971708 73700 17856 S 81,3 1,9 13:22.85 gedit syslog has this: Mar 30 13:50:48 lubuntu dbus[482]: [system] Activating service name='org.freedesktop.hostname1' (using servicehelper) Mar 30 13:50:48 lubuntu dbus[482]: [system] Successfully activated service 'org.freedesktop.hostname1' Mar 30 13:51:36 lubuntu kernel: [212933.326558] CPU2: Core temperature above threshold, cpu clock throttled (total events = 7467) Mar 30 13:51:36 lubuntu kernel: [212933.326559] CPU6: Core temperature above threshold, cpu clock throttled (total events = 7467) Mar 30 13:51:36 lubuntu kernel: [212933.326562] CPU4: Package temperature above threshold, cpu clock throttled (total events = 14104) Mar 30 13:51:36 lubuntu kernel: [212933.326564] CPU5: Package temperature above threshold, cpu clock throttled (total events = 14104) Mar 30 13:51:36 lubuntu kernel: [212933.326566] CPU1: Package temperature above threshold, cpu clock throttled (total events = 14104) Mar 30 13:51:36 lubuntu kernel: [212933.326567] CPU0: Package temperature above threshold, cpu clock throttled (total events = 14104) Mar 30 13:51:36 lubuntu kernel: [212933.326569] CPU3: Package temperature above threshold, cpu clock throttled (total events = 14104) Mar 30 13:51:36 lubuntu kernel: [212933.326571] CPU7: Package temperature above threshold, cpu clock throttled (total events = 14104) Mar 30 13:51:36 lubuntu kernel: [212933.326572] CPU6: Package temperature above threshold, cpu clock throttled (total events = 14104) Mar 30 13:51:36 lubuntu kernel: [212933.326585] CPU2: Package temperature above threshold, cpu clock throttled (total events = 14104) Mar 30 13:51:36 lubuntu kernel: [212933.327540] CPU2: Core temperature/speed normal Mar 30 13:51:36 lubuntu kernel: [212933.327541] CPU6: Core temperature/speed normal Mar 30 13:51:36 lubuntu kernel: [212933.327543] CPU4: Package temperature/speed normal Mar 30 13:51:36 lubuntu kernel: [212933.327544] CPU0: Package temperature/speed normal Mar 30 13:51:36 lubuntu kernel: [212933.327546] CPU1: Package temperature/speed normal Mar 30 13:51:36 lubuntu kernel: [212933.327547] CPU3: Package temperature/speed normal Mar 30 13:51:36 lubuntu kernel: [212933.327550] CPU7: Package temperature/speed normal Mar 30 13:51:36 lubuntu kernel: [212933.327551] CPU5: Package temperature/speed normal Mar 30 13:51:36 lubuntu kernel: [212933.327552] CPU6: Package temperature/speed normal Mar 30 13:51:36 lubuntu kernel: [212933.327561] CPU2: Package temperature/speed normal ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus 1.5.5-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: LXDE Date: Sun Mar 30 16:14:45 2014 InstallationDate: Installed on 2014-03-07 (22 days ago) InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha amd64+mac (20140307) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1299759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
